zmk_mf68/app/tests/momentary-layer/behavior_keymap.dtsi

#include <dt-bindings/zmk/keys.h>
#include <behaviors.dtsi>
#include <dt-bindings/zmk/kscan_mock.h>

/ {
	keymap {
		compatible = "zmk,keymap";
		label ="Default keymap";

		default_layer {
			bindings = <
				&kp B &mo 1
				&trans &trans>;
		};

		layer_1 {
			bindings = <
				&kp C_NEXT &trans
				&trans &trans>;
		};
	};
};
feat(test): add tests for momentary layers 2020-08-29 06:21:31 +10:00			`#include <dt-bindings/zmk/keys.h>`
			`#include <behaviors.dtsi>`
refactor: replace filename hyphens with underscores 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 2020-12-23 02:56:00 +11:00			`#include <dt-bindings/zmk/kscan_mock.h>`
feat(test): add tests for momentary layers 2020-08-29 06:21:31 +10:00
			`/ {`
			`keymap {`
			`compatible = "zmk,keymap";`
			`label ="Default keymap";`

			`default_layer {`
			`bindings = <`
			`&kp B &mo 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-12 02:40:13 +11:00			`&trans &trans>;`
feat(test): add tests for momentary layers 2020-08-29 06:21:31 +10:00			`};`

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-12 02:40:13 +11:00			`layer_1 {`
feat(test): add tests for momentary layers 2020-08-29 06:21:31 +10:00			`bindings = <`
refactor(keys): Unify usage page. * Remove need for separate `&cp` behavior, but keep it for now for backward compat. * Refactor sensor inc/dec as well. 2020-10-26 15:30:24 +11:00			`&kp C_NEXT &trans`
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-12 02:40:13 +11:00			`&trans &trans>;`
feat(test): add tests for momentary layers 2020-08-29 06:21:31 +10:00			`};`
			`};`
			`};`