From 384fef72d3a08f6bdc4e8557caf0bb78953dab32 Mon Sep 17 00:00:00 2001 From: noroadsleft Date: Thu, 21 Feb 2019 15:24:44 -0800 Subject: 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. --- docs/hand_wire.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/hand_wire.md') diff --git a/docs/hand_wire.md b/docs/hand_wire.md index ba2eee7125..697a508052 100644 --- a/docs/hand_wire.md +++ b/docs/hand_wire.md @@ -216,7 +216,7 @@ Farther down are `MATRIX_ROW_PINS` and `MATRIX_COL_PINS`. Change their definitio ### `.h` -The next file you'll want to look at is `.h`. You're going to want to rewrite the `KEYMAP` definition - the format and syntax here is extremely important, so pay attention to how things are setup. The first half of the definition are considered the arguments - this is the format that you'll be following in your keymap later on, so you'll want to have as many k*xy* variables here as you do keys. The second half is the part that the firmware actually looks at, and will contain gaps depending on how you wired your matrix. +The next file you'll want to look at is `.h`. You're going to want to rewrite the `LAYOUT` definition - the format and syntax here is extremely important, so pay attention to how things are setup. The first half of the definition are considered the arguments - this is the format that you'll be following in your keymap later on, so you'll want to have as many k*xy* variables here as you do keys. The second half is the part that the firmware actually looks at, and will contain gaps depending on how you wired your matrix. We'll dive into how this will work with the following example. Say we have a keyboard like this: -- cgit v1.2.3