From 634b277b0710245ec1fbf167e20929aa8f28c020 Mon Sep 17 00:00:00 2001 From: Robert Akhmerov Date: Sat, 16 Nov 2019 20:20:49 +0300 Subject: [PATCH] [Docs] Explain Tap Dance interruption (#5520) --- docs/feature_tap_dance.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/feature_tap_dance.md b/docs/feature_tap_dance.md index 7427a77146..f48f11b1cb 100644 --- a/docs/feature_tap_dance.md +++ b/docs/feature_tap_dance.md @@ -333,6 +333,8 @@ And then simply use `TD(X_CTL)` anywhere in your keymap. If you want to implement this in your userspace, then you may want to check out how [DanielGGordon](https://github.com/qmk/qmk_firmware/tree/master/users/gordon) has implemented this in their userspace. +> In this configuration "hold" takes place **after** tap dance timeout (see `ACTION_TAP_DANCE_FN_ADVANCED_TIME`). To achieve instant hold, remove `state->interrupted` checks in conditions. As a result you may use comfortable longer tapping periods to have more time for taps and not to wait too long for holds (try starting with doubled `TAPPING_TERM`). + ### Example 5: Using tap dance for advanced mod-tap and layer-tap keys Tap dance can be used to emulate `MT()` and `LT()` behavior when the tapped code is not a basic keycode. This is useful to send tapped keycodes that normally require `Shift`, such as parentheses or curly braces—or other modified keycodes, such as `Control + X`.