dadf1e611f
Previously the definition was copied almost 1:1 from the `none` behavior
in order to set up the important files and have a small running, but
featureless sample.
This change introduces a way to actually configure the custom lock
behavior, using the following syntax:
```
behaviors {
dead_lock_prevent {
compatible = "zmk,behavior-custom-lock";
// to define a key
dead: dead_key {
#binding-cells = <2>;
bindings = <&kp>, <&kp>;
}
// or to define a macro
deadm: dead_macro {
#binding-cells = <2>;
bindings = <¯o>, <&kp>;
}
}
}
```
Additionally, there's now no standard definition flying around (deletion
of `dts/behaviors/custom_lock.dtsi`)
Signed-off-by: Sophie Tyalie <dev@flowerpot.me>
|
||
|---|---|---|
| .. | ||
| behaviors | ||
| display | ||
| macros | ||
| vendor-prefixes.txt | ||
| zmk,combos.yaml | ||
| zmk,conditional-layers.yaml | ||
| zmk,ext-power-generic.yaml | ||
| zmk,keymap-sensors.yaml | ||
| zmk,keymap.yaml | ||
| zmk,kscan-composite.yaml | ||
| zmk,kscan-mock.yaml | ||
| zmk,matrix-transform.yaml | ||