doc: additional tip detailing missing &kp
This commit is contained in:
parent
3936298260
commit
ea2d33aa18
1 changed files with 5 additions and 1 deletions
|
@ -58,10 +58,14 @@ A `devicetree_unfixed.h` error that follows with an "undeclared here" string ind
|
||||||
|
|
||||||
In this example, the error string `DT_N_S_keymap_S_symbol_layer_P_bindings_IDX_12_PH_P_label` indicates a problem with the key binding in position `12` in the `symbol_layer` of the keymap.
|
In this example, the error string `DT_N_S_keymap_S_symbol_layer_P_bindings_IDX_12_PH_P_label` indicates a problem with the key binding in position `12` in the `symbol_layer` of the keymap.
|
||||||
|
|
||||||
:::note
|
:::info
|
||||||
Key positions are numbered starting from `0` at the top left key on the keymap, incrementing horizontally, row by row.
|
Key positions are numbered starting from `0` at the top left key on the keymap, incrementing horizontally, row by row.
|
||||||
:::
|
:::
|
||||||
|
|
||||||
|
:::tip
|
||||||
|
A common mistake is to enter the keycodes directly without the leading `&kp` behavior. That is, having entries such as `SPACE` that should have been `&kp SPACE`.
|
||||||
|
:::
|
||||||
|
|
||||||
### Split Keyboard Halves Unable to Pair
|
### Split Keyboard Halves Unable to Pair
|
||||||
|
|
||||||
Split keyboard halves pairing issue can be resolved by flashing a settings reset firmware to both controllers. You will first need to acquire the reset UF2 image file with one of the following options:
|
Split keyboard halves pairing issue can be resolved by flashing a settings reset firmware to both controllers. You will first need to acquire the reset UF2 image file with one of the following options:
|
||||||
|
|
Loading…
Add table
Reference in a new issue