In my VST, I create a ResizableWindow:
m_pWindow = new ResizableWindow(name, true);
It contains a text editor component, and although arrow keys let me traverse the text, I can’t actually type anything. If I create the same component to be shown within the AudioProcessorEditor, then it does let me edit. I’ve ensured that it is not read-only.
Digging into it and breakpointing in windowProc, it appears that the ResizableWindow is not receiving WM_CHAR messages, although it is clearly returning DLGC_WANTALLKEYS. The AudioProcessorEditor correctly receives all WM_CHAR messages.
I’ve seen lots of posts about VST hosts blocking keyboard messages, but in this case, something is blocking the new window–not the primary VST window. I’m using a nearly year-old version of Juce, and I can’t do an update at the moment.
Any idea what could be happening? Do top level windows require some special setup to get WM_CHAR messages?