It isn’t that straightforward.
That is just one example where a user would expect a ( to appear and instead they will get a KEY_DOWN. There are many others. It would be a horrible breaking change and we need to think much more carefully about what we can do.
I don’t think it’s trivial to implement it in JUCE properly, there are lots of edge cases to consider, and it has to play nice in every situation. It was easy to proof-of-concept the approach for a fix, but the actual fix involves pretty much all keyboard handling systems in JUCE, and it needs to be thoroughly tested on many VST3 hosts…
Bump, it’s been a while, any news on this issue? I’d still like to be able to use “space” and “command-x” in an active text editor, while also being able to control Reaper if no UI component consumes key events (like in all other DAWs and Reaper on Windows).
Still an issue as of JUCE 7.0.9.
