Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upward swipes sometimes don't register #937

Open
6 of 7 tasks
Nixill opened this issue Jun 2, 2024 · 3 comments
Open
6 of 7 tasks

Upward swipes sometimes don't register #937

Nixill opened this issue Jun 2, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@Nixill
Copy link
Contributor

Nixill commented Jun 2, 2024

Steps to reproduce

  1. Use a layout that has up-swipes from the top row, such as programmer
  2. Set the swipe length to a number like 70
  3. Swipe upwards on a top-row key such as r, starting your swipe somewhere near the top of the key
  4. 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.

Acknowledgements

  • I have written a short but informative title.
  • I have updated the app to the latest version.
  • I have searched the existing issues and this is a new one, NOT a duplicate or related to another open issue.
  • This is not a question or a discussion, in which case I should have gone to lemmy.ml/c/thumbkey
  • This is a single bug report, in case of multiple bugs I will open a separate issue for each one (they can always link to each other if related)
  • I have admitted that I am a clown by having checked this box, as I have not read these acknowledgements. 🤡
  • I have filled out all of the requested information in this form.
@Nixill Nixill added the bug Something isn't working label Jun 2, 2024
@glm4610
Copy link
Contributor

glm4610 commented Jun 5, 2024

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

@breversa
Copy link
Contributor

breversa commented Jul 5, 2024

I’m having a similar issue with the FR v2 layout:

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.

Thumb-Key 3.2.6
Fairphone 5
/e/OS 2.1 = Android 13

@Noitarud
Copy link

Noitarud commented Dec 5, 2024

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 #

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants