After this commit, I have a problem that the arrow keys are no longer recognized, but only in the plugin (vst/vst3), while in the standalonePlugin it works normally?!
It can easily be reproduced if only FileBrowserComponent is added to PluginEditor… if it is compiled as a plugin, it will not be possible to navigate through the browser using the arrow keys
Maybe the host has keyboard focus. Did you click on the plugin window to take. focus first? (Or call wantsKeyboardFocus(true)?)
Only the arrow keys do not work, as far as I can see, the other keys are registered normally.
Hmm. Maybe you’ll have to put the FileBrowserComponent inside another component? That’s what we do, anyway. Once I click on the list of files itself, my arrow keys work (in all hosts that I know of).
If I go back to the commit before that, everything works normally, I tested with FLStudio and Reaper, on Windows 10
Ah, forgot it was a specific commit you’d mentioned where it changed. We are on an older version still, so we wouldn’t see that. Sorry for the noise.
1 Like
Same happens with page up/down.
@reuk just a reminder to look at
Thanks for reporting. I’ve attempted to fix the issue here:
Keyboard handling in plugins is quite fiddly!
Please try updating, and as always, let us know if you encounter any new issues. Thanks!
1 Like
Looks like it’s fixed, thanks 