aboutsummaryrefslogtreecommitdiff
path: root/docs/quantum_keycodes.md
diff options
context:
space:
mode:
authorXScorpion2 <rcalt2vt@gmail.com>2019-05-12 00:20:14 -0500
committerDrashna Jaelre <drashna@live.com>2019-05-11 22:20:14 -0700
commitc6184d2e7ed9695c22635431394e501b1d5e6271 (patch)
treea720b2371ea7e913c77cfc523088ed5a7a15db4c /docs/quantum_keycodes.md
parentec302295b695e43c5967a6f806c4b4505c651e13 (diff)
downloadqmk_firmware-c6184d2e7ed9695c22635431394e501b1d5e6271.tar.gz
qmk_firmware-c6184d2e7ed9695c22635431394e501b1d5e6271.zip
Added check for event pressed to clear space cadet (#5839)
* Added check for pressed to clear space cadet * Found some docs to update * Update docs/quantum_keycodes.md Co-Authored-By: fauxpark <fauxpark@gmail.com> * Changes from PR
Diffstat (limited to 'docs/quantum_keycodes.md')
-rw-r--r--docs/quantum_keycodes.md7
1 files changed, 6 insertions, 1 deletions
diff --git a/docs/quantum_keycodes.md b/docs/quantum_keycodes.md
index 90192e632..a2ba34c32 100644
--- a/docs/quantum_keycodes.md
+++ b/docs/quantum_keycodes.md
@@ -1,6 +1,6 @@
1# Quantum Keycodes 1# Quantum Keycodes
2 2
3Quantum keycodes allow for easier customisation of your keymap than the basic ones provide, without having to define custom actions. 3Quantum keycodes allow for easier customization of your keymap than the basic ones provide, without having to define custom actions.
4 4
5All keycodes within quantum are numbers between `0x0000` and `0xFFFF`. Within your `keymap.c` it may look like you have functions and other special cases, but ultimately the C preprocessor will translate those into a single 4 byte integer. QMK has reserved `0x0000` through `0x00FF` for standard keycodes. These are keycodes such as `KC_A`, `KC_1`, and `KC_LCTL`, which are basic keys defined in the USB HID specification. 5All keycodes within quantum are numbers between `0x0000` and `0xFFFF`. Within your `keymap.c` it may look like you have functions and other special cases, but ultimately the C preprocessor will translate those into a single 4 byte integer. QMK has reserved `0x0000` through `0x00FF` for standard keycodes. These are keycodes such as `KC_A`, `KC_1`, and `KC_LCTL`, which are basic keys defined in the USB HID specification.
6 6
@@ -16,6 +16,11 @@ On this page we have documented keycodes between `0x00FF` and `0xFFFF` which are
16|`KC_GESC` |`GRAVE_ESC`|Escape when tapped, <code>&#96;</code> when pressed with Shift or GUI| 16|`KC_GESC` |`GRAVE_ESC`|Escape when tapped, <code>&#96;</code> when pressed with Shift or GUI|
17|`KC_LSPO` | |Left Shift when held, `(` when tapped | 17|`KC_LSPO` | |Left Shift when held, `(` when tapped |
18|`KC_RSPC` | |Right Shift when held, `)` when tapped | 18|`KC_RSPC` | |Right Shift when held, `)` when tapped |
19|`KC_LCPO` | |Left Control when held, `(` when tapped |
20|`KC_RCPC` | |Right Control when held, `)` when tapped |
21|`KC_LAPO` | |Left Alt when held, `(` when tapped |
22|`KC_RAPC` | |Right Alt when held, `)` when tapped |
23|`KC_SFTENT` | |Right Shift when held, Enter when tapped |
19|`KC_LEAD` | |The [Leader key](feature_leader_key.md) | 24|`KC_LEAD` | |The [Leader key](feature_leader_key.md) |
20|`KC_LOCK` | |The [Lock key](feature_key_lock.md) | 25|`KC_LOCK` | |The [Lock key](feature_key_lock.md) |
21|`FUNC(n)` |`F(n)` |Call `fn_action(n)` (deprecated) | 26|`FUNC(n)` |`F(n)` |Call `fn_action(n)` (deprecated) |