diff options
author | Drashna Jaelre <[email protected]> | 2019-04-05 12:47:25 -0700 |
---|---|---|
committer | Jack Humbert <[email protected]> | 2019-04-05 15:47:25 -0400 |
commit | 5701b75e3c10728d424ec058d26ef2e354aba0c0 (patch) | |
tree | 979b01e8226d5fb33789bd1c41853c8412bfa669 /docs/config_options.md | |
parent | 4c1760883e2e0ed710348f02bc791786ed0c1b04 (diff) | |
download | qmk_firmware-5701b75e3c10728d424ec058d26ef2e354aba0c0.tar.gz qmk_firmware-5701b75e3c10728d424ec058d26ef2e354aba0c0.zip |
Custom Tapping Term per key (#5009)
* Add customizable tapping terms
* Add Documentation
* Fix function
* Fixes
* It's not a pointer
* Add debugging output
* Update documentation to be at least vaguely accurate
* Use `get_tapping_term(tapping_key.event)` instead
`e` doesn't include column and row information, properly. It registers as 255, regardless of the actual keypress.
However `tapping_key.event` actually gives the correct column and row information. It appears be the correct structure to use.
In fact, it looks like the issue is that `e` is actually the "TICK" structure, as defined in keyboard.h
* Use variable tapping term value rather than define
* Silly drashna - tapping_key.event, not event
* add get_event_keycode() function
* Fix typo
Co-Authored-By: drashna <[email protected]>
* Remove post_process_record_quantum since it's the wrong PR
* Update quantum/quantum.c
Co-Authored-By: drashna <[email protected]>
* Better handle ifdef statement for permissive hold
Since we can't be sure that tapping term is actually 500
* Update quantum.c comments based on feedback
* Clean up get_tapping_term function
Clean up function so that users don't need to call the event function, and instead only check the keycode
* Add ability to run functionality on and off
* Make ifdef's more compact
Diffstat (limited to 'docs/config_options.md')
-rw-r--r-- | docs/config_options.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/config_options.md b/docs/config_options.md index ad42e97802..c5131a8414 100644 --- a/docs/config_options.md +++ b/docs/config_options.md @@ -126,6 +126,8 @@ If you define these options you will enable the associated feature, which may in * `#define TAPPING_TERM 200` * how long before a tap becomes a hold, if set above 500, a key tapped during the tapping term will turn it into a hold too +* `#define TAPPING_TERM_PER_KEY` + * enables handling for per key `TAPPING_TERM` settings * `#define RETRO_TAPPING` * tap anyway, even after TAPPING_TERM, if there was no other key interruption between press and release * See [Retro Tapping](feature_advanced_keycodes.md#retro-tapping) for details |