summaryrefslogtreecommitdiffstats
path: root/keyboards
diff options
context:
space:
mode:
authorNick Choi <iinikchi@gmail.com>2017-05-26 06:19:12 +0200
committerNick Choi <iinikchi@gmail.com>2017-05-26 06:19:12 +0200
commit1bff72c0099d5a59684f912f81ede3f0f0198028 (patch)
treed647d6e8cde552565844c8696712cdbc21f7216b /keyboards
parentd462409762165dadf2e514f084229c45e2c3b0c6 (diff)
downloadqmk_firmware-1bff72c0099d5a59684f912f81ede3f0f0198028.tar.gz
qmk_firmware-1bff72c0099d5a59684f912f81ede3f0f0198028.tar.xz
-
Diffstat (limited to 'keyboards')
-rw-r--r--keyboards/frosty_flake/keymaps/nikchi/variableTapDance.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/keyboards/frosty_flake/keymaps/nikchi/variableTapDance.md b/keyboards/frosty_flake/keymaps/nikchi/variableTapDance.md
index e69de29bb..7b9695a83 100644
--- a/keyboards/frosty_flake/keymaps/nikchi/variableTapDance.md
+++ b/keyboards/frosty_flake/keymaps/nikchi/variableTapDance.md
@@ -0,0 +1,6 @@
+# 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.
+
+- `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.