diff options
| author | Stefan Kerkmann <karlk90@pm.me> | 2022-08-06 12:51:13 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-08-06 20:51:13 +1000 |
| commit | f27b617f36d55ac5469247016a1b79304f892366 (patch) | |
| tree | 3334b3b4cf653fa131eef0729529c06450e12168 /keyboards/40percentclub | |
| parent | e9f9f99a3374ad46e9a2baf2fe35c3f1d0715d4b (diff) | |
[Core] Process all changed keys in one scan loop, deprecate `QMK_KEYS_PER_SCAN` (#15292)
Diffstat (limited to 'keyboards/40percentclub')
| -rw-r--r-- | keyboards/40percentclub/gherkin/keymaps/stevexyz/config.h | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/keyboards/40percentclub/gherkin/keymaps/stevexyz/config.h b/keyboards/40percentclub/gherkin/keymaps/stevexyz/config.h index c708babf16..d837be8ba1 100644 --- a/keyboards/40percentclub/gherkin/keymaps/stevexyz/config.h +++ b/keyboards/40percentclub/gherkin/keymaps/stevexyz/config.h @@ -39,8 +39,6 @@ // how long before oneshot times out #define ONESHOT_TAP_TOGGLE 2 // how many taps before oneshot toggle is triggered - #define QMK_KEYS_PER_SCAN 4 - // Allows sending more than one key per scan. By default, only one key event gets sent via process_record() per scan. This has little impact on most typing, but if you're doing a lot of chords, or your scan rate is slow to begin with, you can have some delay in processing key events. Each press and release is a separate event. For a keyboard with 1ms or so scan times, even a very fast typist isn't going to produce the 500 keystrokes a second needed to actually get more than a few ms of delay from this. But if you're doing chording on something with 3-4ms scan times? You probably want this. #define COMBO_COUNT 2 // Set this to the number of combos that you're using in the Combo feature. #define COMBO_TERM 200 |