You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
With ad0b37f I've noticed double-tap zooming is a little more difficult than it is on Google Maps. I think Google Maps measures the distance between double-tap ACTION_DOWN and ACTION_UP. If it's under a certain threshold (maybe getScaledTouchSlop) then it doesn't count as a quickzoom. Right now, if your finger strays a few pixels after ACTION_DOWN, it's considered a quickzoom even though it was probably just a sloppy double-tap.
The text was updated successfully, but these errors were encountered:
brewin
changed the title
Double-taps aren't detected as often as they should be
[Android] Double-taps are sometimes mistaken for quickzooms
Nov 25, 2015
With ad0b37f I've noticed double-tap zooming is a little more difficult than it is on Google Maps. I think Google Maps measures the distance between double-tap ACTION_DOWN and ACTION_UP. If it's under a certain threshold (maybe getScaledTouchSlop) then it doesn't count as a quickzoom. Right now, if your finger strays a few pixels after ACTION_DOWN, it's considered a quickzoom even though it was probably just a sloppy double-tap.
The text was updated successfully, but these errors were encountered: