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
desktop.MouseHover Button state is not reliable #1533
Comments
Thanks for the report, I think I can see what's wrong. However for:
I'm not sure I can see it. Can you share some code to replicate? |
Also remove old comment - that was supposed to reserve the iota, but it got broken some time ago Fixes fyne-io#1533
Please let me know if #1534 fixes the issue for you @MagicalTux |
Hi, just tested and that works nicely, thanks!! |
Cool, resolved for the pending 1.4.1 release |
Describe the bug:
When using desktop.MouseHover to capture
MouseMoved(MouseEvent)
events in a widget, the button status may not work if both buttons are pressed at the same time.To Reproduce:
Steps to reproduce the behaviour:
Right now mouse buttons are handled as values (iota+1), I believe these should be handled as flags (1<<iota) in order to keep track of multiple buttons used at the same time.
Multiple buttons used at the same time might not be typical in desktop environment, but could happen in games (left button to move forward, right button to fire kind of things for example).
Extra: I'm not sure if it's expected or not, but enabling drag events (Dragged/DragEnd) causes MouseMoved events to not be fired while Button is not zero.
Device (please complete the following information):
The text was updated successfully, but these errors were encountered: