summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCem Aksoylar <caksoylar@gmail.com>2022-02-06 23:03:33 -0800
committerPete Johanson <peter@peterjohanson.com>2022-02-07 09:30:16 -0500
commitc18c3d910653557db3c3e65b1440ee805f1d38cf (patch)
treec02c36e58b0d900d150d59e2f68ae0dc20fe670e
parent76268bae8ffebc304d971342b14cbfcbca2f0b8a (diff)
feat(docs): Add note for combos invoking source-specific behaviors
-rw-r--r--docs/docs/features/combos.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/docs/features/combos.md b/docs/docs/features/combos.md
index 1a19cfe..550bd25 100644
--- a/docs/docs/features/combos.md
+++ b/docs/docs/features/combos.md
@@ -43,6 +43,10 @@ Key positions are numbered like the keys in your keymap, starting at 0. So, if t
- Fully overlapping combos like `0 1` and `0 1 2` are supported.
- You are not limited to `&kp` bindings. You can use all ZMK behaviors there, like `&mo`, `&bt`, `&mt`, `&lt` etc.
+:::note Source-specific behaviors on split keyboards
+Invoking a source-specific behavior such as one of the [reset behaviors](behaviors/reset.md) using a combo will always trigger it on the central side of the keyboard, regardless of the side that the keys corresponding to `key-positions` are on.
+:::
+
### Advanced configuration
There are three global combo parameters which are set through KConfig. You can set them in the `<boardname>.conf` file in the same directory as your keymap file.