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
Use a layout that has up-swipes from the top row, such as programmer
Set the swipe length to a number like 70
Swipe upwards on a top-row key such as r, starting your swipe somewhere near the top of the key
Swipe up-left on a top-row key such as r, again starting your swipe somewhere near the top of the key
Expected behavior
The upward (3) and up-left (4) gestures should be input, such as ^ or "
Actual behavior
The tap (3) or left (4) gestures are input, such as r or <.
version of the program
3.2.1
Android version
Android 13
Device
Google Pixel 6a
Other details
Phone is rooted and using LineageOS 20-20231104-NIGHTLY-bluejay (I should really update that...)
It feels to me like the phone is treating the swipe as never going higher than the top of the keyboard. Notably, a swipe upwards from the bottom of the key will work, same as a swipe upwards from the bottom of the h key will still produce a q even if you don't swipe into the r key, but it is noticeably harder to get an up-swipe from the top row than from another row.
This is something I mentioned in another issue, which happens because of how Android clamps the pointer motion data to within the IME window. Because of that, we can't properly track user gestures which wander upwards. I think Unexpected Keyboard has a good workaround for this. I'll take a look at it this week
In the top-left square, the top-right symbol (the french apostrophe "'") rarely registers properly : it’s the right symbol ("^") that is input, unless I very precisely swipe in a not-totally-but-almost vertical way (= in the 1 o’clock direction from the center of the square).
As far as I know, it doesn’t happen with other squares/positions.
rightward guestures on right keys (redo, cut and whatever … is) and upward guestures on top (settings) do not work.
perhaps abstractly related: noted the rightward stroke ")" is difficult to enter, only possible if I swipe from left side instead of centre.
To fix rightward, move a little from edge(#783). Topward doesn't matter for me(move from (invisible) top?!) but adds confusion, place on bksp or fixed down-right #
Steps to reproduce
Expected behavior
The upward (3) and up-left (4) gestures should be input, such as
^
or"
Actual behavior
The tap (3) or left (4) gestures are input, such as
r
or<
.version of the program
3.2.1
Android version
Android 13
Device
Google Pixel 6a
Other details
Phone is rooted and using LineageOS 20-20231104-NIGHTLY-bluejay (I should really update that...)
It feels to me like the phone is treating the swipe as never going higher than the top of the keyboard. Notably, a swipe upwards from the bottom of the key will work, same as a swipe upwards from the bottom of the h key will still produce a q even if you don't swipe into the r key, but it is noticeably harder to get an up-swipe from the top row than from another row.
Acknowledgements
The text was updated successfully, but these errors were encountered: