[Core] Process all changed keys in one scan loop, deprecate QMK_KEYS_PER_SCAN (#15292)

This commit is contained in:
Stefan Kerkmann
2022-08-06 12:51:13 +02:00
committed by GitHub
parent e9f9f99a33
commit f27b617f36
96 changed files with 90 additions and 607 deletions

View File

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