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
I am struggling to find a tool that would measure how much time my fingers take to press and release a key or, more accurately, how long keys remain activated for on average (an maybe low and high percentiles) while I type.
I use home row modifiers, which require character keys to act differently when they are held than when they are pressed. The tools I use (mainly keyd and Kanata) allow me to specify a timeout value that represents how long a key should be activated for before being considered as held. Ideally, that value should be above my slowest activation time while typing. This value will probably be very personal, change overtime and be influenced by the keyboard used during the test.
If ttyper could collect and display that info it would become a great tool for the keyboard customization community. Thanks.
The text was updated successfully, but these errors were encountered:
argenkiwi
changed the title
[Feature] Key activation time stat
[Feature] Keystroke dwelling (or key-hold) time stat
May 24, 2024
I am struggling to find a tool that would measure how much time my fingers take to press and release a key or, more accurately, how long keys remain activated for on average (an maybe low and high percentiles) while I type.
I use home row modifiers, which require character keys to act differently when they are held than when they are pressed. The tools I use (mainly keyd and Kanata) allow me to specify a timeout value that represents how long a key should be activated for before being considered as held. Ideally, that value should be above my slowest activation time while typing. This value will probably be very personal, change overtime and be influenced by the keyboard used during the test.
If ttyper could collect and display that info it would become a great tool for the keyboard customization community. Thanks.
The text was updated successfully, but these errors were encountered: