aboutsummaryrefslogtreecommitdiff
path: root/docs/faq_keymap.md
diff options
context:
space:
mode:
authorRyan <fauxpark@gmail.com>2021-11-04 16:22:17 +1100
committerGitHub <noreply@github.com>2021-11-03 22:22:17 -0700
commitf529580860cf5a1de4afc10432f218a45daae17a (patch)
tree1d2fa041174f2586230ab831c05e5b56d8ba4f92 /docs/faq_keymap.md
parentb06d9d822cfb72e0728b11711a333f2f5d3c631e (diff)
downloadqmk_firmware-f529580860cf5a1de4afc10432f218a45daae17a.tar.gz
qmk_firmware-f529580860cf5a1de4afc10432f218a45daae17a.zip
Basic keycode overhaul (#14726)
Diffstat (limited to 'docs/faq_keymap.md')
-rw-r--r--docs/faq_keymap.md12
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/faq_keymap.md b/docs/faq_keymap.md
index dbeadba71..01ded4f23 100644
--- a/docs/faq_keymap.md
+++ b/docs/faq_keymap.md
@@ -19,7 +19,7 @@ There are 3 standard keyboard layouts in use around the world- ANSI, ISO, and JI
19Sometimes, for readability's sake, it's useful to define custom names for some keycodes. People often define custom names using `#define`. For example: 19Sometimes, for readability's sake, it's useful to define custom names for some keycodes. People often define custom names using `#define`. For example:
20 20
21```c 21```c
22#define FN_CAPS LT(_FL, KC_CAPSLOCK) 22#define FN_CAPS LT(_FL, KC_CAPS)
23#define ALT_TAB LALT(KC_TAB) 23#define ALT_TAB LALT(KC_TAB)
24``` 24```
25 25
@@ -38,8 +38,8 @@ As a quick fix try holding down `Space`+`Backspace` while you plug in your keybo
38 38
39The key found on most modern keyboards that is located between `KC_RGUI` and `KC_RCTL` is actually called `KC_APP`. This is because when that key was invented there was already a key named `MENU` in the relevant standards, so MS chose to call that the `APP` key. 39The key found on most modern keyboards that is located between `KC_RGUI` and `KC_RCTL` is actually called `KC_APP`. This is because when that key was invented there was already a key named `MENU` in the relevant standards, so MS chose to call that the `APP` key.
40 40
41## `KC_SYSREQ` Isn't Working 41## `KC_SYSTEM_REQUEST` Isn't Working
42Use keycode for Print Screen(`KC_PSCREEN` or `KC_PSCR`) instead of `KC_SYSREQ`. Key combination of 'Alt + Print Screen' is recognized as 'System request'. 42Use keycode for Print Screen (`KC_PRINT_SCREEN`/`KC_PSCR`) instead of `KC_SYSTEM_REQUEST`. Key combination of 'Alt + Print Screen' is recognized as 'System request'.
43 43
44See [issue #168](https://github.com/tmk/tmk_keyboard/issues/168) and 44See [issue #168](https://github.com/tmk/tmk_keyboard/issues/168) and
45* https://en.wikipedia.org/wiki/Magic_SysRq_key 45* https://en.wikipedia.org/wiki/Magic_SysRq_key
@@ -47,7 +47,7 @@ See [issue #168](https://github.com/tmk/tmk_keyboard/issues/168) and
47 47
48## Power Keys Aren't Working 48## Power Keys Aren't Working
49 49
50Somewhat confusingly, there are two "Power" keycodes in QMK: `KC_POWER` in the Keyboard/Keypad HID usage page, and `KC_SYSTEM_POWER` (or `KC_PWR`) in the Consumer page. 50Somewhat confusingly, there are two "Power" keycodes in QMK: `KC_KB_POWER` in the Keyboard/Keypad HID usage page, and `KC_SYSTEM_POWER` (or `KC_PWR`) in the Consumer page.
51 51
52The former is only recognized on macOS, while the latter, `KC_SLEP` and `KC_WAKE` are supported by all three major operating systems, so it is recommended to use those instead. Under Windows, these keys take effect immediately, however on macOS they must be held down until a dialog appears. 52The former is only recognized on macOS, while the latter, `KC_SLEP` and `KC_WAKE` are supported by all three major operating systems, so it is recommended to use those instead. Under Windows, these keys take effect immediately, however on macOS they must be held down until a dialog appears.
53 53
@@ -57,7 +57,7 @@ https://github.com/tmk/tmk_keyboard/issues/67
57 57
58## Modifier/Layer Stuck 58## Modifier/Layer Stuck
59Modifier keys or layers can be stuck unless layer switching is configured properly. 59Modifier keys or layers can be stuck unless layer switching is configured properly.
60For Modifier keys and layer actions you have to place `KC_TRANS` on same position of destination layer to unregister the modifier key or return to previous layer on release event. 60For Modifier keys and layer actions you have to place `KC_TRNS` on same position of destination layer to unregister the modifier key or return to previous layer on release event.
61 61
62* https://github.com/tmk/tmk_core/blob/master/doc/keymap.md#31-momentary-switching 62* https://github.com/tmk/tmk_core/blob/master/doc/keymap.md#31-momentary-switching
63* https://geekhack.org/index.php?topic=57008.msg1492604#msg1492604 63* https://geekhack.org/index.php?topic=57008.msg1492604#msg1492604
@@ -75,7 +75,7 @@ This feature is for *mechanical lock switch* like [this Alps one](https://deskth
75 75
76After enabling this feature use keycodes `KC_LCAP`, `KC_LNUM` and `KC_LSCR` in your keymap instead. 76After enabling this feature use keycodes `KC_LCAP`, `KC_LNUM` and `KC_LSCR` in your keymap instead.
77 77
78Old vintage mechanical keyboards occasionally have lock switches but modern ones don't have. ***You don't need this feature in most case and just use keycodes `KC_CAPS`, `KC_NLCK` and `KC_SLCK`.*** 78Old vintage mechanical keyboards occasionally have lock switches but modern ones don't have. ***You don't need this feature in most case and just use keycodes `KC_CAPS`, `KC_NUM` and `KC_SCRL`.***
79 79
80## Input Special Characters Other Than ASCII like Cédille 'Ç' 80## Input Special Characters Other Than ASCII like Cédille 'Ç'
81 81