From 1d182995ed71ba6d014a6e3360ef39e5d33cfbfb Mon Sep 17 00:00:00 2001 From: Nick Brassel Date: Mon, 27 Feb 2023 08:41:42 +1100 Subject: Breaking Changes 2023q1 changelog. (#19945) --- docs/ChangeLog/20230226/PR17007.md | 31 ------------------------------- 1 file changed, 31 deletions(-) delete mode 100644 docs/ChangeLog/20230226/PR17007.md (limited to 'docs/ChangeLog/20230226/PR17007.md') diff --git a/docs/ChangeLog/20230226/PR17007.md b/docs/ChangeLog/20230226/PR17007.md deleted file mode 100644 index bea04994b5..0000000000 --- a/docs/ChangeLog/20230226/PR17007.md +++ /dev/null @@ -1,31 +0,0 @@ -`TAPPING_FORCE_HOLD` feature is now replaced by `QUICK_TAP_TERM`. Instead of turning off auto-repeat completely, user will have the option to configure a `QUICK_TAP_TERM` in milliseconds. When the user holds a tap-hold key after tapping it within `QUICK_TAP_TERM`, QMK will send the tap keycode to the host, enabling auto-repeat. - -Its value is set to `TAPPING_TERM` by default and it can be reduced to match typing habits to avoid false triggers. To disable auto-repeat completely, set `QUICK_TAP_TERM` to zero. - -`TAPPING_FORCE_HOLD_PER_KEY` is also deprecated and replaced by `QUICK_TAP_TERM_PER_KEY`. The old granular control function for tapping force hold is: - -```c -bool get_tapping_force_hold(uint16_t keycode, keyrecord_t *record) { - switch (keycode) { - case LT(1, KC_BSPC): - return true; - default: - return false; - } -} -``` - -That function can be replaced with: - -```c -uint16_t get_quick_tap_term(uint16_t keycode, keyrecord_t *record) { - switch (keycode) { - case SFT_T(KC_SPC): - return 0; - default: - return QUICK_TAP_TERM; - } -} -``` - -For more details, please read the updated documentation section on [Quick Tap Term](tap_hold.md#quick-tap-term). -- cgit v1.2.3