diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2021-04-05 22:28:26 -0700 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2021-04-05 22:37:27 -0700 |
commit | 143cce94eea904ef025c94238fe3541b87ad694e (patch) | |
tree | 594a28c8f9008fc812ce09403c09fcddacf81168 /301array-equal.subx | |
parent | 316bf37541c820e3c9d4b6640f4db324c4b2963b (diff) | |
download | mu-143cce94eea904ef025c94238fe3541b87ad694e.tar.gz |
support for arrow keys
Mu's keyboard handling is currently a bit of a mess, and this commit might be a bad idea. Ideally keyboards would return Unicode. Currently Mu returns single bytes. Mostly ASCII. No support for international keyboards yet. ASCII and Unicode have some keyboard scancodes grandfathered in, that don't really make sense for data transmission. Like backspace and delete. However, other keyboard scancodes don't have any place in Unicode. Including arrow keys. So Mu carves out an exception to Unicode for arrow keys. We'll place the arrow keys in a part of Unicode that is set aside for implementation-defined behavior (https://en.wikipedia.org/wiki/C0_and_C1_control_codes#C1_controls): 0x80: left arrow 0x81: down arrow 0x82: up arrow 0x83: right arrow The order is same as hjkl for mnemonic convenience. I'd _really_ to follow someone else's cannibalization here. If I find one later, I'll switch to it. Applications that blindly assume the keyboard generates Unicode will have a bad time. Events like backspace, delete and arrow keys are intended to be processed early and should not be in text. With a little luck I won't need to modify this convention when I support international keyboards.
Diffstat (limited to '301array-equal.subx')
0 files changed, 0 insertions, 0 deletions