drashna/qmk_firmware
1
0
Fork 0
Code Activity Actions

matrix_scan_x -> x_task (#13748)

Browse source
This commit is contained in:
Joel Challis 2021-07-28 12:01:23 +01:00 • committed by GitHub
parent c52c69d45f
commit 03d258c222
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
13 changed files with 27 additions and 31 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/feature_tap_dance.md
View file

@ -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.