-
-
Notifications
You must be signed in to change notification settings - Fork 860
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] hasGesture
is false
after double tap zoom in onPositionChanged
callback
#1465
Comments
Might be that line 71 of geatures/gestures.dart needs to include "hasGesture: true," if you wanted to test that. |
I looked into the code and your suggestion seems reasonable.I tried to edit it in my .pub-cache folder to quickly try it out, though changes there didn't have an effect in my project. I am not familiar with flutter package development, so I would be happy if someone who knows about flutter package development and open source contribution could try it out. |
Hi @David-Prelinger, |
Thanks I'll try it out! |
Hi @David-Prelinger, just checking up to see if you ever got around to this? No problem if not! |
Hi @JaffaKetchup sorry for not coming back to this sooner. This issue was work related and we decided not to follow through with fixing it since it was only a minor inconvenience to us. |
No problem! |
hasGesture
is false
after double tap zoom in onPositionChanged
callback
What is the bug?
The onPositionChanged callback delivers false for
hasGesture
when zooming, especially double tapping to zoom. Normally, when the user zooms with two fingers, he also moves the map slightly, so hasGesture will eventually be true. But if you zoom with mouse and keyboard or zoom via double tap,hasGesture
is just false.This makes it hard to disguish between zooms made by code and zooms made by human.
What is the expected behaviour?
hasGesture == true, when onPositionChanged callback is called from a zoom.
How can we reproduce this issue?
Do you have a potential solution?
No response
Can you provide any other information?
I was just able to test it on Android, but I expect it to happen on all platforms.
Platforms Affected
Android
Severity
Minimum: Allows normal functioning
Frequency
Consistently: Always occurs at the same time and location
Requirements
flutter doctor
finds no relevant issuesThe text was updated successfully, but these errors were encountered: