-
Notifications
You must be signed in to change notification settings - Fork 383
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
"Accept background input" Does not work with Lua Console / Lua Scripts #671
Comments
I dont' think it should be expected at all that "Accept background input" works on tool dialogs of bizhawk itself. Each tool has to decide to accept mainform input. Tools like tastudio do this (and it is a very tricky thing to consider). If I could edit this ticket I would change it to request mainform input on the lua console and lua created dialogs. |
Persists in 2.3.1. Easiest "solution" is to change |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
The hack has become a feature (as of 7596b97). Have your ext. tool form inherit
Back on-topic, the Lua Console could override |
Open for 7 years? Yeah let's close wontfix |
Hotkeys are broken in other ways too, even on Windows... It's just hard to do this right with WinForms. Remember also the mouse isn't passed through (the prop should be I'll be changing the setting's description as above. |
AcceptBackgroundInput_Test.zip
What steps will reproduce the problem?
What is the expected output? What do you see instead?
Expected: BizHawk would respond to input when focus is on Lua Console or Lua Script
(Ideally there would even be an option to "Accept background input from any BizHawk-generated window" or something to that effect. But at least it would be good to have the current option function across BizHawk generated windows.
Actual: BizHawk does not respond to input when focus is on Lua Console or Lua Script
What version of the product are you using? On what operating system?
Emuhawk 1.11.6 on Windows 10
The text was updated successfully, but these errors were encountered: