-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Bug] Swiping in the monthly view is glitchy #2172
Comments
its not glitchy, you are just triggering pull to refresh by down gesture. You can disable it in the app Settings -> Enable pull-to-refresh from the top. |
Considering that no other app has this issue when swiping to the side, this is not proper behaviour. Normally, what apps will do is if they detect that you are making, for example, a horizontal swipe gesture, they will block all other gestures from interrupting. What's happening here is that the horizontal swipe gesture was started and then was interrupted by the swipe down gesture by a minute amount of displacement in the y-direction during the swipe. If a horizontal gesture is made, movements in the y-direction should be ignored completely. |
@tibbi It is glitchy. The standard behaviour with multi-directional swipes is that, once a swipe crosses a threshold distance on one axis, it can no longer trigger gestures for another axis. You have to cancel by returning your digit's tip to its origin then begin a new swipe in order to use the other axis. In this case, it should stop paying attention to any vertical movement because it's way too easy to trigger a partial "pull to refresh", >90% of the way through a swipe. Humans typically make a slight arc, given we use our hands, especially in single-handed use. To expect near perfectly straight swipes is unrealistic. Your response was quite dismissive. It's a real usability issue. I'm sure it's practically impossible to operate for anyone with even a slight tremor. |
As shown in the following video, swiping in the monthly view is really glitchy.
screen-20230820-133317.mp4.2.mp4.2.mp4
The text was updated successfully, but these errors were encountered: