diff options
| author | Joel Challis <git@zvecr.com> | 2021-07-28 12:01:23 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-07-28 12:01:23 +0100 |
| commit | 03d258c2226959480fc3ead1568ca2fe8ba37c59 (patch) | |
| tree | 6a5f05f6017ec01ea68883749bc5af0e558a51cf /docs/feature_tap_dance.md | |
| parent | c52c69d45f180e8ab677be4707ea2c8180a14254 (diff) | |
matrix_scan_x -> x_task (#13748)
Diffstat (limited to 'docs/feature_tap_dance.md')
| -rw-r--r-- | docs/feature_tap_dance.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/feature_tap_dance.md b/docs/feature_tap_dance.md index 5d77f3e08d..f4e989921f 100644 --- a/docs/feature_tap_dance.md +++ b/docs/feature_tap_dance.md @@ -50,7 +50,7 @@ The main entry point is `process_tap_dance()`, called from `process_record_quant This means that you have `TAPPING_TERM` time to tap the key again; you do not have to input all the taps within a single `TAPPING_TERM` timeframe. This allows for longer tap counts, with minimal impact on responsiveness. -Our next stop is `matrix_scan_tap_dance()`. This handles the timeout of tap-dance keys. +Our next stop is `tap_dance_task()`. This handles the timeout of tap-dance keys. For the sake of flexibility, tap-dance actions can be either a pair of keycodes, or a user function. The latter allows one to handle higher tap counts, or do extra things, like blink the LEDs, fiddle with the backlighting, and so on. This is accomplished by using an union, and some clever macros. |