zmk.git/app/tests/momentary-layer/1-normal, branch master ZMK Bluetooth keyboard firmware. feature(modifiers): add explicit modifiers 2021-01-25T04:30:41+00:00 Okke Formsma okke@formsma.nl 2021-01-22T16:00:19+00:00 7b7701ae90469b920cd78e2ab7aca0c470140b7a 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. 
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.
refactor: replace filename hyphens with underscores 2020-12-28T06:15:35+00:00 innovaker 66737976+innovaker@users.noreply.github.com 2020-12-22T15:56:00+00:00 842aa5a842e117b7b00e49258ca0bde44dc0c789 Aligns *.h and *.c to underscore naming convention. These were kept (with warnings) for backwards compatibility with external boards/shields: - kscan-mock.h - matrix-transform.h They should be removed in the future. PR: #523 
Aligns *.h and *.c to underscore naming convention.

These were kept (with warnings) for backwards compatibility with external boards/shields:
- kscan-mock.h
- matrix-transform.h
They should be removed in the future.

PR: #523
 fix momentary layer bug when top layer is not &trans 2020-11-16T22:19:27+00:00 Okke Formsma okke@formsma.nl 2020-11-11T15:40:13+00:00 e48a6b659c6da4afd56f2c3e3fa56d291ebf80e4 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. 
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.