-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
MouseButton input bug when captured #1009
Comments
I just realized it only quits working when moving the mouse too far to the left. Other directions don't cause the problem |
I was able to workaround it be setting the cursor position every frame. I think it could possibly be an X11, KDE Plasma, or perhaps winit bug, but I haven't narrowed it down yet. For now I'm fine with just setting the cursor position. Edit: and it doesn't happen full screen. Only when the window is on the left side of the screen so maybe it has something to do with KDE's cursor screen edge detection. |
I don't think this is necessarily a bug, since it is more expected behavior that the window shouldn't get mouse events when it leaves the window, in games you might want to lock the cursor using |
Their example does lock the cursor |
Ah true, I'm not entirely sure then, I'm guessing that the locking might've been erroring out for whatever reason, I don't think we really logged that before or that was overlooked in the logs? |
A bit late but the issue no longer exists with cursor |
Bevy version
Commit: 1398d78
Operating system & version
Linux
I have a high DPI display which may or may not be relevant.
What you did
When mouse is captured if you move the mouse to one side mouse button input quits working.
I made an example where whenever you click the ClearColor changes
The first time you click you're mouse will also get captured
Here's a reproducible example:
What you expected to happen
MouseButton input should work no matter how far you move the mouse.
What actually happened
When moving the mouse too far to the side MouseButton input quits working.
The text was updated successfully, but these errors were encountered: