You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add-on hardware support (eg. audio, RGB, OLED screen, etc.)
Alteration (enhancement/optimization) of existing feature(s)
New behavior
Description
Hello,
I am working with the QMK firmware and I'm looking to customize the behavior of my keyboard. Specifically, I want to adjust the key press delay by defining the interval at which the keyboard matrix is scanned. I've searched through the QMK docs and codebase, but I have not found any macros or functions that seem to allow this adjustment.
Could you please provide guidance on how to define the matrix scan interval, or point me to the relevant part of the documentation if it exists?
Thank you for your assistance.
The text was updated successfully, but these errors were encountered:
As far as I know, you can measure the matrix scan frequency, but you cannot explicitly set the scan interval. I guess part of the reason is QMK supports wide range of different MCUs which vary significantly in performance. However, there's a hardware option to modify the delay between changing matrix pin state and reading values, try #define MATRIX_IO_DELAY. After all, a typical matrix scan is just a series of "changing row pin state and reading column pin values".
Feature Request Type
Description
Hello,
I am working with the QMK firmware and I'm looking to customize the behavior of my keyboard. Specifically, I want to adjust the key press delay by defining the interval at which the keyboard matrix is scanned. I've searched through the QMK docs and codebase, but I have not found any macros or functions that seem to allow this adjustment.
Could you please provide guidance on how to define the matrix scan interval, or point me to the relevant part of the documentation if it exists?
Thank you for your assistance.
The text was updated successfully, but these errors were encountered: