| |
| |
On 6/17/22 19:08 Bill Spitzak wrote:
I'm pretty certain all platforms queue up events. X certainly does.
However it is not hard for bugs or badly-written code to cause the
RELEASE event to be sent the wrong place.
It probably is best for the counter (and anywhere else timeouts are
repeated) to check if the mouse button is still held down. This
indicator is set when the event is processed even if the event is not
delivered to the right place.
Yep, I did this and it catches even the case when a modal dialog window
is opened in the callback. This works sufficiently because the event
state etc. (Fl::event_*) is "sticky" - I know that's your work, Bill
(thanks!), just for others reading here.
--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/f6f61888-e5ab-9d8e-ba7e-5e4158629c84%40online.de.
[ Direct Link to Message ] | |
|
| |
FLTK Apps 
