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
It would be nice to be able to configure how long it takes to go from "tapping" to "holding". For example, I want to lengthen the time you need to hold the key, as I keep flipping the keyboard when I actually mean to just add a space.
The text was updated successfully, but these errors were encountered:
That's interesting, since it's not based on timing at all, merely on ordering. Have a look at the test cases to see what I mean. If you run Keyb with a debugger attached, and then repro the issue, you'll see logs for every character you type, and you'll be able to see specifically what order of events causes the misfire. If you do that, we can write a test case and fix it 🙂
Huh! I made an incorrect assumption. I'll definitely check the test cases out.
That being the situation, then, I think it strengthens the case for adding the ability to use a dedicated keybinding, as in #23. The current implementation introduces a bit of delay between when you tap the spacebar and when the space gets typed. I realize that some delay has to be introduced for that to work, but it throws me off, because apparently I'm really picky? A dedicated keybinding would let me avoid a delay, while also allowing greater interop with other keyboards/accessibility devices, or even scripting things like HammerSpoon.
It would be nice to be able to configure how long it takes to go from "tapping" to "holding". For example, I want to lengthen the time you need to hold the key, as I keep flipping the keyboard when I actually mean to just add a space.
The text was updated successfully, but these errors were encountered: