zmk/app/tests/momentary-layer/4-nested/keycode_events.snapshot

mo_pressed: position 1 layer 1
mo_pressed: position 0 layer 2
kp_pressed: usage_page 0x07 keycode 0x05 implicit_mods 0x00 explicit_mods 0x00
kp_released: usage_page 0x07 keycode 0x05 implicit_mods 0x00 explicit_mods 0x00
mo_released: position 0 layer 2
mo_released: position 1 layer 1
feat(test): add tests for momentary layers 2020-08-28 13:21:31 -07:00			`mo_pressed: position 1 layer 1`
fix momentary layer bug when top layer is not &trans Key release events released keys on the wrong layer if the 'top layer' was not &trans above the &mo key. base <&mo 1> layer 1 <&kp B> This was caused by overwriting `zmk_keymap_active_behavior_layer[position]` after the &mo key was handled. 2020-11-11 07:40:13 -08:00			`mo_pressed: position 0 layer 2`
feature(modifiers): add explicit modifiers this makes LS(LEFT_CONTROL) work as if shift and control were both pressed explicitly. Previously, the left shift would have been released as soon as another key was pressed. The implicit behavior is useful in case of LS(NUMBER_1) when rolling over to other keys. Also see #361. 2021-01-22 08:00:19 -08:00			`kp_pressed: usage_page 0x07 keycode 0x05 implicit_mods 0x00 explicit_mods 0x00`
			`kp_released: usage_page 0x07 keycode 0x05 implicit_mods 0x00 explicit_mods 0x00`
fix momentary layer bug when top layer is not &trans Key release events released keys on the wrong layer if the 'top layer' was not &trans above the &mo key. base <&mo 1> layer 1 <&kp B> This was caused by overwriting `zmk_keymap_active_behavior_layer[position]` after the &mo key was handled. 2020-11-11 07:40:13 -08:00			`mo_released: position 0 layer 2`
feat(test): add tests for momentary layers 2020-08-28 13:21:31 -07:00			`mo_released: position 1 layer 1`