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.
The problem is that we are calculating a LatLng from screencoordinates left of the dateline while using a LatLng from screencoordinates from the right side of the dateline. This conflicts and results in a incorrect touch target.
Discussed this a bit with @brunoabinader and decided this is a platform specific problem and should be solved in the Android SDK itself.
The text was updated successfully, but these errors were encountered:
To visualise this issue see next clip:
The problem is that we are calculating a LatLng from screencoordinates left of the dateline while using a LatLng from screencoordinates from the right side of the dateline. This conflicts and results in a incorrect touch target.
Discussed this a bit with @brunoabinader and decided this is a platform specific problem and should be solved in the Android SDK itself.
The text was updated successfully, but these errors were encountered: