QMK (and Kanata)
https://midwest.social/post/17202886
=> More informations about this toot | More toots from sxan@midwest.social
It looks like the feature is called Auto Shift in QMK/VIAL (I had to open up VIAL to remember the term).
Iβm not sure I have a good answer for quick typing, I was in the process of implementing urobβs timeless homerow mods for ZMK when I fried my ZMK board. I know there are QMK implementations (maybe in userspace?), but my quick googling didnβt come up with what I was thinking.
=> More informations about this toot | More toots from unmoored@awful.systems
For QMK, my go-to hrm-embetterment came from Achordion. Not sure if that helps OP, but it made hrm amazing for me, and it does the sort of timing tweaks that might help here.
Otherwise, the HOLD_ON_OTHER_KEY_PRESS mode might help.
=> More informations about this toot | More toots from dnzm@feddit.nl
Thanks for the suggestions.
Auto Shift is a neat idea; I suspect adding yet another delay factor would be counter-productive, for me, though. The whole shift/press/release-shift/release-shift issue is more about typing faster than my brain actually works, such that Iβm not always consistent in which order I release keys. Adding a lag to get caps would be, I think, infuriating.
However, the timeless homerow mod looks fantastic. Need to think a little more about their solution, but itβs encouraging in that (a) they sound like they have exactly my problem, and (b) they found a solution for it. Itβs a great resource, thank you!
=> More informations about this toot | More toots from sxan@midwest.social
QMK has pretty extensive documentation that Iβm pretty sure covers this. Have you read Tap-Hold Configuration Options?
=> More informations about this toot | More toots from hedgehog@ttrpg.network
I⦠had not. The permissive hold option looks like it might address my second issue, that of the fact that the fixed timing is incongruent with my far less consistent human timing.
Someone else mentioned the timeless homerow mods, wherein positional hold-tap is used to address rolling issues, which is what I think Iβm seeing with the shift-down/char-down/shift-up/char-up sequence not outputting the expected shifted character.
Thanks for pointing me back at the documentation. TBH, Iβm a bit overwhelmed by the number of configurable options in QMK, and suffer information overload: pointers like that help me figure out where to start fiddling. Working with QMK, even through the incredibly convenient Vial application, makes me feel like sitting in front of a Moog synthesizer.
=> More informations about this toot | More toots from sxan@midwest.social This content has been proxied by September (3851b).Proxy Information
text/gemini