-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mouse release event ignored if released too quickly #91
Comments
Fixed in fd0feef. |
This was initially fixed for me, but I think it broke again in 0d1ccd7. I think the issue is with this if statement:
All press and release events will be eaten regardless of |
Oops... must've been on autopilot there. Fixed again in baca24c. |
I'm experiencing issues on my end with unconsumed events sticking around, so I am going to disable this behavior & reopen this issue until this is fully fixed. |
I've just completed a more proper solution of this in c637ad6. This issue should be resolved; just let me know if you see any other manifestations of the same thing. |
It seems fixed for the menu items and tabs, but the text view widget seems to ignore the down event now as well (text cursor doesn't update). |
Can you show a video of what you're seeing? I am not seeing that on my end. |
I think I see one potential issue - you might be expecting whatever mouse positions are attached to the mouse press/release events (presumably auto-generated) to show up in the selection itself, without forcibly changing what the mouse position is? If that's the case, can you expand on the intended use case you have in mind for that? |
click2.mp4Yeah, the fast click events are auto-generated to reproduce it consistently for video.
(Also tested with a Logitech mouse macro, and my actual use case, remote desktop.) |
Ahhhhh okay makes perfect sense, thanks. Looks like I've fixed this on my end in 11dd5fd. Can you give that a try? |
Seems to be working! 👍 |
If you depress the left mouse button, and release it too quickly, the release event seems to be ignored.
For example, if you do it over a line in the text view widget it'll be stuck selecting text afterwards, but it also happens with other widgets (menu items and tabs).
Here is a recording of it happening, by sending automated down and up events without any delay to reproduce it consistently:
click.mp4
The text was updated successfully, but these errors were encountered: