> Still, I consider this a hack / workaround rather than a real platform > feature. > Any reason to bind the actions shortcut to the notion of focused component ?
Yes. :-) By definition, key events go to the component that currently has the focus and propagate up the component hierarchy from there. When a key press event reaches a Window (i.e. has not been consumed on the way up), if an action mapping exist for the keystroke, it is executed. If no component has the focus, then there is no way for a keystroke to reach the window. In practice, it is fairly unusual for no component to have the focus. Why not focus a default component when your window opens? All you'd need to do is call window.requestFocus() in a windowOpened() listener. G
