Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Define the matrix scan interval to adjust key press delay #23209

Open
1 of 4 tasks
boulevard-h opened this issue Mar 4, 2024 · 1 comment
Open
1 of 4 tasks

Comments

@boulevard-h
Copy link

Feature Request Type

  • Core functionality
  • 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.

@myst729
Copy link
Contributor

myst729 commented Mar 12, 2024

What are you going to do?

If you want to change the default tap-hold threshold, try #define TAPPING_TERM. If your want to deal with the physical switch contact bounce, try #define DEBOUNCE.

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".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants