-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
Keyboard input in REAPER does not work #38
Comments
This fixes keyboard input in REAPER, and I haven't found any downsides to this approach yet.
This issue also affected Ardour in some instances. I'm currently going through a bunch of plugins to see if they all work as expected in all different hosts with the new input focus grabbing method. The current fix does not seem to work reliably with Melda's 'F1' help dialogs in REAPER and Ardour, so I'm still working on that. EDIT: As of e680f2e this should now work again. I'll have to do some more rigorous testing to see if this does not introduce any regressions elsewhere. EDIT2: I ended up completely rewriting how keyboard input is handled to be simpler, more reliable, and to be able to give input focus back to the host when needed (can be useful in REAPER). This seems to fix all issues with REAPER and Ardour, and hotkeys in Bitwig while the editor window is open now also work again, but it will require some more testing to see if this does not cause any unwanted behaviour. |
Now that yabridge 1.7.0 is out this should be resolved. Please let me know if anyone's having any other keyboard input related issues. |
Keyboard input in REAPER currently does not work. The window handling in REAPER is quite different from some other DAWs which complicates things a little. Alt-tabbing out of the plugin window and then alt-tabbing back in again will enable keyboard focus, but that's definitely not how things should work. I have not yet come up with a way around this other than aggressively grabbing keyboard focus whenever you hover your mouse over the window, which is not a great solution.
The text was updated successfully, but these errors were encountered: