mirror of
https://github.com/qmk/qmk_firmware.git
synced 2026-09-29 21:38:47 +02:00
add docusaurus, convert notes/tips, ids
This commit is contained in:
+2
-2
@@ -3,7 +3,7 @@
|
||||
QMK keymaps are defined inside a C source file. The data structure is an array of arrays. The outer array is a list of layer arrays while the inner layer array is a list of keys. Most keyboards define a `LAYOUT()` macro to help you create this array of arrays.
|
||||
|
||||
|
||||
## Keymap and Layers :id=keymap-and-layers
|
||||
## Keymap and Layers {#keymap-and-layers}
|
||||
In QMK, **`const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS]`** holds multiple **layers** of keymap information in **16 bit** data holding the **action code**. You can define **32 layers** at most.
|
||||
|
||||
For trivial key definitions, the higher 8 bits of the **action code** are all 0 and the lower 8 bits holds the USB HID usage code generated by the key as **keycode**.
|
||||
@@ -27,7 +27,7 @@ Respective layers can be validated simultaneously. Layers are indexed with 0 to
|
||||
|
||||
Sometimes, the action code stored in keymap may be referred as keycode in some documents due to the TMK history.
|
||||
|
||||
### Keymap Layer Status :id=keymap-layer-status
|
||||
### Keymap Layer Status {#keymap-layer-status}
|
||||
|
||||
The state of the Keymap layer is determined by two 32 bit parameters:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user