I left feedback on this one, but perhaps I'm missing something and
there's an easy workaround.
http://www.realsoftware.com/feedback/viewreport.php?reportid=kqjinqab
When the user uses tab (for example) to select elements of the user
interface that do not implement keydown (but which do implement
keyboard actions, like a focused checkbox toggling on the space
key), keys that do not affect the control are swallowed; the
window's keydown handler never sees them.
Consider the case where the programmer wants to create a hotkey,
say ESC, that she wants to be available at all times. If the user
happens to hit tab and focus on a checkbox (or other non-keydown
controls), then suddenly ESC stops working, and there's no way for
the checkbox to pass on the key, since it doesn't implement keydown.
I suggest that keys that do not result in a change to the control's
state be passed on to the control's parent.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>