summaryrefslogtreecommitdiffstats
path: root/keyboards/frosty_flake/keymaps/nikchi/variableTapDance.md
diff options
context:
space:
mode:
authorNick Choi <iinikchi@gmail.com>2017-05-26 15:59:34 -0400
committerNick Choi <iinikchi@gmail.com>2017-05-26 15:59:34 -0400
commit66e9cf9718770206f68e33a7f88b46ed372ff2a4 (patch)
treed338da7d86fd182291b45658bb2a571b037d1b94 /keyboards/frosty_flake/keymaps/nikchi/variableTapDance.md
parent1bff72c0099d5a59684f912f81ede3f0f0198028 (diff)
clarified tap
Diffstat (limited to 'keyboards/frosty_flake/keymaps/nikchi/variableTapDance.md')
-rw-r--r--keyboards/frosty_flake/keymaps/nikchi/variableTapDance.md7
1 files changed, 5 insertions, 2 deletions
diff --git a/keyboards/frosty_flake/keymaps/nikchi/variableTapDance.md b/keyboards/frosty_flake/keymaps/nikchi/variableTapDance.md
index 7b9695a83a..b2e5041393 100644
--- a/keyboards/frosty_flake/keymaps/nikchi/variableTapDance.md
+++ b/keyboards/frosty_flake/keymaps/nikchi/variableTapDance.md
@@ -1,6 +1,9 @@
# Tap Dancing to different beats.
-Tap Dance is constrained normally by `TAPPING_TERM` defined in your keyboard's config.h This proves to be challenging to work with when sometimes you just need more time to tap out your dance.
+Tap Dance is constrained normally by `TAPPING_TERM` defined in your keyboard's config.h This proves to be challenging to work with when sometimes you just need more time to tap out your dance, or even a different "beat".
+
+
+
+- `ACTION_TAP_DANCE_FN_ADVANCED_TIME(user_fn_on_each_tap, user_fn_on_dance_finished, user_fn_on_dance_reset, tap_specific_tapping_term)` : This works the same as `ACTION_TAP_DANCE_FN_ADVANCED` just with the extra `tap_specific_tapping_term` arguement at the end. This way you can set a specific tap dance to have a longer or shorter tap in between your taps, giving you more, or less, time in between each tap.
-- `ACTION_TAP_DANCE_FN_ADVANCED_TIME(user_fn_on_each_tap, user_fn_on_dance_finished, user_fn_on_dance_reset, tap_specific_tapping_term)` : This works the same as `ACTION_TAP_DANCE_FN_ADVANCED` just with the extra `tap_specific_tapping_term` arguement at the end.
`tap_specific_tapping_term` should be the same type and range of values that one would put into the `TAPPING_TERM` definition in the config.h file.