-
Notifications
You must be signed in to change notification settings - Fork 199
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
[EDIT] MonthView on Android: swipe behavior when the screen is Swiped #661
Comments
I'm not sure if I fully understand the behavior. Ideally it you select on a date, the current month view will be swiped to the month of that day. For example, if current month is October, if you select any date in October, the view should remain the same. If you select Nov 1st, it will navigate to November. |
I don't understand why it's doing this either... The module is a copy-paste from the doc, I haven't added anything more. I "corrected" the problem by blocking swipes, but it's not a real fix. |
Hi, I'm coming back to you with the same problem, I've figured out what's going on. When I swipe, it doesn't update the month I've just swiped. (today = January) If I swipe right, it stays on January and doesn't update the view to February. If I swipe again, it updates to February (when I should be on the March slide) and when I touch the screen on my phone, it updates to the right month (in this case March because I swiped twice) It works fine on Windows in the test phase, but not on Android. I've max upgrade my dependencies : |
How do you fix it? |
@Shadufi Have the same issue. Are you finding a solution? |
Hello
My problem is mainly on phone (Android) because on PC, it works perfectly.
There is a problem when I try to select a day on the MonthView. When I do this, it swipes to the right if I touch my screen on the right side, and vice versa for the left side.
Note: I've noticed that if I select the same date, it swipes me on the same date but one month before/after.
I've set true to lockSwipes to avoid this strange behavior, but it's preventing me from using the addon to its full potential.
Do you have a solution?
The text was updated successfully, but these errors were encountered: