Changes between Initial Version and Version 3 of Ticket #6123
- Timestamp:
- Mar 28, 2021, 8:15:39 PM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #6123 – Description
initial v3 1 Example case: you have two different hotkeys.[[BR]][[BR]]"hotkeyA" : "H"[[BR]]"hotkeyB" : "Ctrl+H"[[BR]][[BR]]both have an onKeyDown handler defined.1 Example case: you have two different hotkeys.[[BR]][[BR]]"hotkeyA" : "Ctrl+H"[[BR]]"hotkeyB" : "H"[[BR]][[BR]]both have an onKeyDown handler defined. 2 2 3 3 1) press Ctrl+H: an event "hotkeyA" type "hotkeydown" is fired, the handler is executed[[BR]]2) release only Ctrl: an event "hotkeyA" type "hotkeyup" is fired AND at the same time (meaning processed in the same tick or whatever is it) and event "hotkeyB" of type "hotkeydown" is fired, the handler for "hotkeyB" is executed 4 4 5 What changed from a23 to a24 that didn't cause this problem? "hotkeyB" wasn't triggered at the same time "hotkeyA" was released, instead it was (ignored implicitly?) executed when the event fired a little more after (the OS keyboard wait time before a pressed key repeats, aprox 500 ms in my case) and the initial "hotkeydown" for "hotkey down" was never fired.5 What changed from a23 to a24 that didn't cause this problem? "hotkeyB" wasn't triggered at the same time "hotkeyA" was released, instead it was (ignored implicitly?) executed when the event fired a little more after (the OS keyboard wait time before a pressed key repeats, aprox 500 ms in my case) and the initial "hotkeydown" for "hotkeyB" was never fired. 6 6 7 7 Possible solutions:[[BR]]A) Filter out all "hotkeydown" hotkeys from being processed if on the list of events to be processed there is at least one event of type "hotkeyup"
