From 070028734cb8ecc8e5502336281a3cb9d0029000 Mon Sep 17 00:00:00 2001 From: Pete Johanson Date: Fri, 18 Dec 2020 15:52:53 +0000 Subject: [PATCH] fix(docs): Tweak overview of behaviors. * New shield behavior docs are slightly out of date. --- docs/docs/development/new-shield.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/docs/development/new-shield.md b/docs/docs/development/new-shield.md index 306f1b3f..8e959bda 100644 --- a/docs/docs/development/new-shield.md +++ b/docs/docs/development/new-shield.md @@ -364,11 +364,12 @@ The two `#include` lines at the top of the keymap are required in order to bring ### Keymap Behaviors -Further documentation on behaviors and bindings is forthcoming, but a summary of the current behaviors you can bind to key positions is as follows: +For full details on the available behaviors, refer to [Behaviors - Key Press](/docs/behaviors/key-press) and read from there. A quick summary of some available behaviors you can use: - `kp` is the "key press" behavior, and takes a single binding argument of the key code from the 'keyboard/keypad" HID usage table. - `mo` is the "momentary layer" behaviour, and takes a single binding argument of the numeric ID of the layer to momentarily enable when that key is held. - `trans` is the "transparent" behavior, useful to be place in higher layers above `mo` bindings to be sure the key release is handled by the lower layer. No binding arguments are required. +- `none` is the "none" behavior, useful to be place in higher layers above `mo` bindings to prevent the key position press/release being handled by the lower layer. No binding arguments are required. - `mt` is the "mod-tap" behavior, and takes two binding arguments, the modifier to use if held, and the keycode to send if tapped. ## Adding Features