>> That's what I was suggesting as well. The simplest solution is to modify >> DisplayHost to send the keystroke to its corresponding Display instance if >> no component currently has the focus. >> > Can you clarify the 'no component currently has the focus' part? Are > you saying this would only occur if there is no Pivot Component in the > entire app?
No - I'm talking about the case when Component#getFocusedComponent() returns null (for example, when an application starts up but fails to request initial focus to some component). If any component has the focus, the key event will bubble up to the display, so this workaround wouldn't be necessary.
