summaryrefslogtreecommitdiffstats
path: root/docs/feature_split_keyboard.md
diff options
context:
space:
mode:
authorQMK Bot <hello@qmk.fm>2023-03-06 19:25:38 +0000
committerQMK Bot <hello@qmk.fm>2023-03-06 19:25:38 +0000
commitc1dfcfc571b8910eeea636d92a12f87f217f2521 (patch)
tree70c4340fd1d81caf86df17d605af5cd14ceceb57 /docs/feature_split_keyboard.md
parent97522bd58a7e21bdb1db2c7d9054e9f8ecbfd04a (diff)
parentf067f4230538ee1efbeaebf13c92106f973ffe93 (diff)
Merge remote-tracking branch 'origin/master' into develop
Diffstat (limited to 'docs/feature_split_keyboard.md')
-rw-r--r--docs/feature_split_keyboard.md10
1 files changed, 10 insertions, 0 deletions
diff --git a/docs/feature_split_keyboard.md b/docs/feature_split_keyboard.md
index 25f7473bda..c095c8712f 100644
--- a/docs/feature_split_keyboard.md
+++ b/docs/feature_split_keyboard.md
@@ -79,6 +79,16 @@ If you're using a custom transport (communication method), then you will also ne
SPLIT_TRANSPORT = custom
```
+### Layout Macro
+
+Configuring your layout in a split keyboard works slightly differently to a non-split keyboard. Take for example the following layout. The top left numbers refer to the matrix row and column, and the bottom right are the order of the keys in the layout:
+
+![Physical layout](https://i.imgur.com/QeY6kMQ.png)
+
+Since the matrix scanning procedure operates on entire rows, it first populates the left half's rows, then the right half's. Thus, the matrix as QMK views it has double the rows instead of double the columns:
+
+![Matrix](https://i.imgur.com/4wjJzBU.png)
+
### Setting Handedness
By default, the firmware does not know which side is which; it needs some help to determine that. There are several ways to do this, listed in order of precedence.