Many times (not all), after a keyboard shortcut is
used, the next keystroke is "eaten". This may be a
result of problems with the KeystrokeGrabber or
ShortcutGrabber.
The ShortcutGrabber class was blocking all key events until
a KEY_TYPED event was encountered. There are some key
strokes that send only KEY_PRESSED and KEY_RELEASED events.
The ShortcutGrabber class now unblocks the events as soon as
a KEY_RELEASED event is encountered. This is fine for any
other KEY_RELEASED events but there is concern that
KEY_TYPED events will still get through and be processed
even though they should not be. More testing will help
solidify the problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=586169
The ShortcutGrabber class was blocking all key events until
a KEY_TYPED event was encountered. There are some key
strokes that send only KEY_PRESSED and KEY_RELEASED events.
The ShortcutGrabber class now unblocks the events as soon as
a KEY_RELEASED event is encountered. This is fine for any
other KEY_RELEASED events but there is concern that
KEY_TYPED events will still get through and be processed
even though they should not be. More testing will help
solidify the problem.