Closed qokrb2t closed 2 months ago
Thanks for the suggestion.
An other cons is that the layouts are already pretty full and free spots are needed for the keys (often dead-keys) that are automatically added to the layouts depending on the user's installed languages. There can be a lot of these for some users, and it's only going to increase over time. Making room for the uppercase swipe would also be a big change to layouts.
This PR makes uppercase accessible via a clockwise circle gesture: https://github.com/Julow/Unexpected-Keyboard/pull/640 You can find the debug build here: https://github.com/Julow/Unexpected-Keyboard/actions/runs/9213480758?pr=640
I think the new circle gesture should answer this issue. Please re-open with suggestions otherwise.
Rats, that build won't install over the previous 1.28+ debug build!
This patch is released.
The access to uppercase in unexpected right now is costlier as i see it (2 keypresses for a single letter & '3+number of letters' keypresses of 'a number of letters')
As a fan of the short-swipes, i'd like to request the developers to explore the possibility of a short-swipe for an uppercase. To any-one of the corners or even to an edge(upper?).
My case,
What goes against my case is a possibility of smart features (Auto-complete, Next word suggestion, Spell-check, Auto-capitalize first letter etc) in the coming versions
My counter is, it's a performance cost. If unexpected as is, takes a 100us to perform an action & a feature implementation takes it to 200us, it still is a 100% performance cost even if we may not notice & even when the h/w is perfectly capable of handling it as normal
I'm not against the smart feature's bucketlist of a traditional virtual keyboard development. Just that it'd be convenient for users who wish to disable(given an option) it