-
Notifications
You must be signed in to change notification settings - Fork 5
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
Touch controls sometimes are inconsistently responsive #100
Comments
Does it happen before or after v1.0.23 release or both? There was a pretty big change on how touches are handled in that release. |
It was happening even before. I'm not able to say if now it happens more frequently, maybe a little bit. |
Ok, will try to have a look |
I had a look and I could not reproduce this issue on my phone. This is exactly what I fixed in v1.0.23 btw, try v1.0.28 and if you have the same issue, please make a screen recording from the launch of the app until when the issue happens. |
Now seems to work way better, thanks. After your update seems is harder to trigger two directions at once, in fact I had to force is using my thumb. I made a screen record like you asked, towards the end I trigger this behaviour more consistently. |
Issue is marked as stale since there has been no activity for two weeks. It will be automatically closed in 5 days. |
Hello, I noticed a good amount of times touch controls "lose" completely or partially the input, making difficult to set some parameters or producing mistakes.
Example: when I try to set effects to notes, I press shift+up and then navigate the effects with the directional buttons. However, lots of time looks like the app loses my touch on the shift button, closing the effect table and bringing me back to the notes screen with the last effect selected.
On M8 webdisplay this was not happening, could be due to the larger area of each button? (M8 Webdisplay reproduce the size of original M8 buttons, scaling them to the display).
Device: Poco F2 with Android 13
The text was updated successfully, but these errors were encountered: