Fixes for issue #10924
https://github.com/wxWidgets/wxWidgets/pull/23944
(1 file)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Thanks, but could you please extract this into a trivial function in the beginning of this file, to make updating it later easier?
And, in fact, thinking more about it, I think we may want to amend this slightly by breaking from the loop after some big (1000? 10000?) number of iterations, just to be 100% sure that we don't get stuck forever if the user has a vibrating mouse generating events all the time or something other like this, which seems impossibly contrived and unrealistic until you run into it in practice...
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
No worries - I'll get onto this later.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
@charvey2718 pushed 1 commit.
—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
@vadz I've done as you requested. Can you see the improvements as part of this PR or do I need to renew it somehow?
charvey2718 is fine for the change log, thanks.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Thanks! I'm going to merge this in master with some minor changes (mostly more comments to explain what's going on here and, also, a better commit message) soon and also apply it to 3.2 branch so that it is included in the upcoming 3.2.3 release.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Closed #23944.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Please note: This is a general problem for any dialog containing a wxListBox for example (probably any control that processes a double-click). If the handler dismisses the dialog, the left-up or move events may happen after the dialog is dismissed...
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()