summaryrefslogtreecommitdiff
path: root/keyboards/lucid
diff options
context:
space:
mode:
authorkiilerix <mads@kiilerich.com>2022-03-05 05:58:50 +0100
committerGitHub <noreply@github.com>2022-03-05 15:58:50 +1100
commitda6d6ce2e1f266892badbd42fb8c6735e61e784f (patch)
treeb5e64da206540e60e01a0fc262c13fa5353d68f3 /keyboards/lucid
parent82dd84e257db8e5fd1eb33c152a0026ee5bee7fe (diff)
Some docs improvements (#15845)
* docs: clarify in "Keymap Overview" what LAYOUT is and isn't It is not strictly necessary to use LAYOUT macros in keyboard.c, but it is a convenient abstraction of hardware internals, allowing focus on the physical keyboard layout. From the C source point of view LAYOUT is macro with a parameter list, which expands to a array of rows that each is an array with a keyboard scancode for each column. A macro parameter list is not an array, and even less a single array. Perhaps no big deal, but also no reason to give incorrect hints. * docs: update "Understanding QMK's Code" to current code structure introduced in 96e2b13d1de This part of the documentation was no longer correct. I tried updating it, mainly copy editing and using github links to latest release. This is not trying to fix all problems, but just trying to fix some problems while reusing much of the old phrases and structure. * Update docs to use "qmk format-python"
Diffstat (limited to 'keyboards/lucid')
0 files changed, 0 insertions, 0 deletions