diff options
| author | QMK Bot <hello@qmk.fm> | 2022-12-14 14:44:19 +0000 |
|---|---|---|
| committer | QMK Bot <hello@qmk.fm> | 2022-12-14 14:44:19 +0000 |
| commit | e2ab98f9601049a7540bd89cb128669b09c688d5 (patch) | |
| tree | 38658d944aad8cdd8b3190ca42e6ce479d55eaa4 /docs/feature_tap_dance.md | |
| parent | 1124bbc1db8fb26418bded7016c702de469b162f (diff) | |
| parent | 99174edf0affb3a62af43a14aefde0b3bd944271 (diff) | |
Merge remote-tracking branch 'origin/master' into develop
Diffstat (limited to 'docs/feature_tap_dance.md')
| -rw-r--r-- | docs/feature_tap_dance.md | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/docs/feature_tap_dance.md b/docs/feature_tap_dance.md index cbee4d0c34..1062e32243 100644 --- a/docs/feature_tap_dance.md +++ b/docs/feature_tap_dance.md @@ -356,8 +356,6 @@ qk_tap_dance_action_t tap_dance_actions[] = { 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. 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 :id=example-5 |