-
Notifications
You must be signed in to change notification settings - Fork 86
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
Default ReaConsole shortcut doesn't work #877
Comments
Confirmed here (on Windows). |
It works on macOS. Setting the FVIRTKEY flag in the fVirt member of the action's ACCEL struct fixes it on both Linux and Windows. EDIT: Commit a1507f7 broke that shortcut on Windows while fixing it on macOS (but not Linux). |
Thanks for the fix @cfillion . Just a thought, I (and I assume some other users) have currently assigned "C" to some other action. Wouldn't this lead to a potential conflict now if "C" gets re-assigned also as default shortcut for the console (as Reaper doesn't allow same shortcut for different actions, what will happen ?) |
From my tests, REAPER ignores the shortcut suggested by extensions if the key was set on another action before (even if the shortcut was removed since and the key is now unused). |
So it seems fine I think, thanks for testing. |
I've tried this on two difference machines (both Windows) with both a regular installation and portable.
If I check the keyboard shortcut for ReaConsole and it says 'C' but that doesn't work. If I remove that and re-set it to 'C' it works fine.
Before fixing it once I tried assigning 'C' to another random command and it didn't warn me about the shortcut already being used.
The text was updated successfully, but these errors were encountered: