From investigating this bug report for ReSynth I believe it has uncovered a bug in Renoise.
I have a function which (through subfunctions) initialises a bunch of stuff, creates a viewbuilder dialog and displays it with a keyhandler that returns all keyboard input back to Renoise.
This function allows the computer keyboard to play sounds.
When this function is called from a created menu entry it works fine.
When called from a keybinding entry, the dialog gets focus but the keyboard doesn’t react the same way (it doesn’t appear to be bound to anything at all - neither the dialog nor Renoise’s main window)
You know, I keep encountering this same “loss of keyboard input to renoise” when i cmd-tab back to Renoise and a gui is open. So I do hope that fixing this bug you’ve reported will also fix that.
(I lose keyboard input in ReSynth and in your FM tool, when cmd-tabbing back to renoise)
If I have mxb’s gui open and chosen, and cmd-tab away from renoise, and then click on the gui to get back, the pckeyboard does function. If I instead just cmd-tab away and cmd-tab back, the fact that a gui is open will result in my pckeyboard jamming going nowhere. I hope this is detailed enough to break it down, when taken in context with my first response to your question.
Also, if the script gui is open, and press CMD-T (add new track), the keyboard input is lost, until i click on the pattern editor again.
(this doesn’t require any cmd-tabbing) so the gui’s keyhandler chokes if i press cmd-t in it