diff options
| author | noroadsleft <xxiinophobia@yahoo.com> | 2019-02-22 00:24:44 +0100 |
|---|---|---|
| committer | Drashna Jaelre <drashna@live.com> | 2019-02-22 08:19:26 +0100 |
| commit | 384fef72d3a08f6bdc4e8557caf0bb78953dab32 (patch) | |
| tree | 547202f9e3be33692c5c49920c176e5f4f057396 /docs/porting_your_keyboard_to_qmk_(arm_and_other_chibios_cpus).md | |
| parent | 8a2346eda1e9fbdec71adf023a1337d5536fe1fa (diff) | |
| download | qmk_firmware-384fef72d3a08f6bdc4e8557caf0bb78953dab32.tar.gz qmk_firmware-384fef72d3a08f6bdc4e8557caf0bb78953dab32.tar.xz | |
Replace instances of KEYMAP with LAYOUT
Many instances in the QMK Docs referenced KEYMAP macros, which is outdated terminology.
Replaced most instances of KEYMAP with LAYOUT, to reflect the desired usage.
Diffstat (limited to 'docs/porting_your_keyboard_to_qmk_(arm_and_other_chibios_cpus).md')
| -rw-r--r-- | docs/porting_your_keyboard_to_qmk_(arm_and_other_chibios_cpus).md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/porting_your_keyboard_to_qmk_(arm_and_other_chibios_cpus).md b/docs/porting_your_keyboard_to_qmk_(arm_and_other_chibios_cpus).md index 50d291a23..c32c428cf 100644 --- a/docs/porting_your_keyboard_to_qmk_(arm_and_other_chibios_cpus).md +++ b/docs/porting_your_keyboard_to_qmk_(arm_and_other_chibios_cpus).md @@ -54,10 +54,10 @@ This is where all of the custom logic for your keyboard goes - you may not need ## `/keyboards/<keyboard>/<keyboard>.h` -Here is where you can (optionally) define your `KEYMAP` function to remap your matrix into a more readable format. With ortholinear boards, this isn't always necessary, but it can help to accommodate the dead spots on your matrix, where there are keys that take up more than one space (2u, staggering, 6.25u, etc). The example shows the difference between the physical keys, and the matrix design: +Here is where you can (optionally) define your `LAYOUT` function to remap your matrix into a more readable format. With ortholinear boards, this isn't always necessary, but it can help to accommodate the dead spots on your matrix, where there are keys that take up more than one space (2u, staggering, 6.25u, etc). The example shows the difference between the physical keys, and the matrix design: ``` -#define KEYMAP( \ +#define LAYOUT( \ k00, k01, k02, \ k10, k11 \ ) \ |