diff options
| author | Sven Gothel <[email protected]> | 2013-01-29 21:27:57 +0100 |
|---|---|---|
| committer | Sven Gothel <[email protected]> | 2013-01-29 21:27:57 +0100 |
| commit | 90e136b65a10d8daf8c3a2df6cc193e55a63722c (patch) | |
| tree | 863f8a3679a70065b031aaf83bd7cc6053fd69ab /src/newt/native/KeyEvent.h | |
| parent | 2f63a43fd6ff9964251c43e248c51bc821f3ecbd (diff) | |
Fix Bug 678: Deliver key-char value for printable chars on all KeyEventListener (-> On Windows as well)
The following is observed, where t0 and t1 refer to subsequent different timestamps:
NEWT delivery order:
PRESSED (t0), RELEASED (t1) and TYPED (t1)
WINDOWS delivery order:
PRESSED (t0), TYPED (t0) and RELEASED (t1)
Windows Auto-Repeat:
PRESSED (t0), TYPED (t0)
Hence we changed the event reorder-code in NEWT to trigger NEWT-PRESSED on
Windows-TYPED for printable chars, assuring key-char values on all listener callbacks.
- KeyEvent.getKeyChar(): Removed disclaimer dedicated for Windows
- Keyevent.isActionKey(): Completed for all NEWT non-printable action keys; Added static variant
- Keyevent.isPrintableKey(): NEW: returns !isModifierKey(keyCode) && !isActionKey(keyCode) ; With static variant
- Windows WindowDriver:
- EVENT_KEY_PRESSED handles non-printable chars only
- EVENT_KEY_TYPE handles printable chars only
- Native: VK_DELETE passes keyCode
- Unit tests: Wait for completion 1s -> 2s
Diffstat (limited to 'src/newt/native/KeyEvent.h')
0 files changed, 0 insertions, 0 deletions