-
Notifications
You must be signed in to change notification settings - Fork 5
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
Input seems to stop after toggling options and settings menu and F11 #295
Comments
I think I may have a fix for this. I don't want to unilaterally declare victory yet... try it out! |
It's I just tested with 2.12.0.20 and it's improved, but still happens when you toggle fullscreen or run aroiund the menus, but if you show the about dialoge and close it seems to fix inputs again. |
Cool, I just got the latest version and spammed the emulater and the UI and it didn't loose imputs. Closing now. |
Just one thing, if you bring up the debugger it seems to loose input then, not sure if this is a quick fix or a pain, but thought I would let you know. |
I can repro a variant of this issue on Linux with 2.13. When starting any game, input isn't working. If I toggle full screen with F11, then input starts working normally. |
My fix to this issue was very Windows-specific; it involved a Win32 CBT hook: The Windows issue was that Qt simply did not go through great lengths to ensure that the "Qt focus" and the "Win32 focus" were in sync. It is very possible that a similar issue is at play in the X11 world but you're on your own. |
**Input seems to stop after toggling options and settings menu. UPDATE: I just noticed F11 does this too.
The text was updated successfully, but these errors were encountered: