Kaleidoscope

Commit Graph

Author	SHA1	Message	Date
Michael Richters	4a63fe1440	Replace the keymap cache with a keyboard state array This replaces the `Layer.live_composite_keymap_[]` cache with a representation of the keyboard's current state as an array of `Key` objects, one per key on the keyboard. In this new array, an idle key will have the value `Key_Transparent`, and a pressed key will have the value of whatever key it's currently mapped to in the keymap (or whatever value the active set of plugins has assigned to it). A value of `Key_NoKey` will mask that key until it is released. If a plugin returns `ABORT` from its `onKeyswitchEvent()` handler, that means that the keymap cache should not be updated. It's especially important to have this occur after plugins like OneShot and Qukeys, where the key can stay active (or become active) after the physical keyswitch has been released. Signed-off-by: Michael Richters <gedankenexperimenter@gmail.com>	4 years ago

Author

SHA1

Message

Date

Michael Richters

4a63fe1440

Replace the keymap cache with a keyboard state array

This replaces the `Layer.live_composite_keymap_[]` cache with a representation
of the keyboard's current state as an array of `Key` objects, one per key on the
keyboard. In this new array, an idle key will have the value `Key_Transparent`,
and a pressed key will have the value of whatever key it's currently mapped to
in the keymap (or whatever value the active set of plugins has assigned to
it). A value of `Key_NoKey` will mask that key until it is released.

If a plugin returns `ABORT` from its `onKeyswitchEvent()` handler, that means
that the keymap cache should not be updated. It's especially important to have
this occur after plugins like OneShot and Qukeys, where the key can stay
active (or become active) after the physical keyswitch has been released.

Signed-off-by: Michael Richters <gedankenexperimenter@gmail.com>

1 Commits (afa32435319e386c73fd13cedc2939c1c624c8f2)