aboutsummaryrefslogtreecommitdiff
path: root/docs/tap_hold.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/tap_hold.md')
-rw-r--r--docs/tap_hold.md19
1 files changed, 19 insertions, 0 deletions
diff --git a/docs/tap_hold.md b/docs/tap_hold.md
index 9ffbfde8f..aacff4004 100644
--- a/docs/tap_hold.md
+++ b/docs/tap_hold.md
@@ -179,6 +179,25 @@ Holding and releasing a dual function key without pressing another key will resu
179 179
180For instance, holding and releasing `LT(2, KC_SPACE)` without hitting another key will result in nothing happening. With this enabled, it will send `KC_SPACE` instead. 180For instance, holding and releasing `LT(2, KC_SPACE)` without hitting another key will result in nothing happening. With this enabled, it will send `KC_SPACE` instead.
181 181
182For more granular control of this feature, you can add the following to your `config.h`:
183
184```c
185#define RETRO_TAPPING_PER_KEY
186```
187
188You can then add the following function to your keymap:
189
190```c
191bool get_retro_tapping(uint16_t keycode, keyrecord_t *record) {
192 switch (keycode) {
193 case LT(2, KC_SPACE):
194 return true;
195 default:
196 return false;
197 }
198}
199```
200
182## Why do we include the key record for the per key functions? 201## Why do we include the key record for the per key functions?
183 202
184One thing that you may notice is that we include the key record for all of the "per key" functions, and may be wondering why we do that. 203One thing that you may notice is that we include the key record for all of the "per key" functions, and may be wondering why we do that.