SpaceCadet was sending a keyswitch event with the row & column coordinates of the wrong key. The coordinates were coming from the keypress, but the injected event was for a previously-pressed (different) key that's still held. With the mutable `live_composite_keymap_[]` change, this meant that pressing (and holding) `shift` then another key would result in only a single character, rather than a repeating character. Regardless of the minor bug, using the row & col for the event was still logically incorrect here. Signed-off-by: Michael Richters <gedankenexperimenter@gmail.com>pull/502/head
parent
66f79c7cbd
commit
81d34bbd88
Loading…
Reference in new issue