> How does the event system in your setup distinguish single- and =
> double-click operations for the left button?
>
> Is it possible that mechanism is somehow eating the clicks if they are =
> too fast, because of the mechanism for deciding whether it is single or =
> double?
>
on the x server side, it adds the queued event on each click (doesn't attempt
to detect double click), I only follwed it to the mouse adding to the queue,
which it was, but sometime between the then and the app, it gets lost, yeah I
saw some time stuff but at that point it was just checking that it didn't go
backwards. Also, the reason why wbar/otherstuff worked is because it detects
buttonrelease, not buttonpress, so anyway, it's just that machine, maybe
someday I'll follow it all the way down to see if openbox or something else is
eating it somehow? weird that right click was fine, so yeah, maybe some add in
as well doing some double click detection (but returning button up). Don't
recall if i found why the keydown/keyup is being reported. for now, skipping
it.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
