summaryrefslogtreecommitdiff
path: root/app/tests/momentary-layer/1-normal/keycode_events.snapshot
diff options
context:
space:
mode:
authorOkke Formsma <okke@formsma.nl>2020-11-11 16:40:13 +0100
committerPete Johanson <peter@peterjohanson.com>2020-11-16 17:19:27 -0500
commite48a6b659c6da4afd56f2c3e3fa56d291ebf80e4 (patch)
treeb1d4d267a28feb380f7c28df76a006b3070a46fa /app/tests/momentary-layer/1-normal/keycode_events.snapshot
parent2871dca9bfce2588e23da0905d7142ef5ff1c1a1 (diff)
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.
Diffstat (limited to 'app/tests/momentary-layer/1-normal/keycode_events.snapshot')
-rw-r--r--app/tests/momentary-layer/1-normal/keycode_events.snapshot4
1 files changed, 4 insertions, 0 deletions
diff --git a/app/tests/momentary-layer/1-normal/keycode_events.snapshot b/app/tests/momentary-layer/1-normal/keycode_events.snapshot
new file mode 100644
index 0000000..608ce09
--- /dev/null
+++ b/app/tests/momentary-layer/1-normal/keycode_events.snapshot
@@ -0,0 +1,4 @@
+mo_pressed: position 1 layer 1
+kp_pressed: usage_page 0x07 keycode 0x06 mods 0x00
+kp_released: usage_page 0x07 keycode 0x06 mods 0x00
+mo_released: position 1 layer 1