Skip to content
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.

[android] incorrect latlngBounds in the VisibleRegion when map is rotated #11219

Merged
merged 1 commit into from
Feb 16, 2018

Conversation

osana
Copy link
Contributor

@osana osana commented Feb 16, 2018

fixed visibleRegion.latlngBounds for rotated map

closes #11137

be created using LatLngBounds.fromLatLngs()
as the order matters in that method and that does not work for rotated map
@osana osana added the Android Mapbox Maps SDK for Android label Feb 16, 2018
@osana osana added this to the android-v6.0.0 milestone Feb 16, 2018
@osana osana requested a review from tobrun February 16, 2018 03:02
@osana osana merged commit 341eb76 into master Feb 16, 2018
@tobrun
Copy link
Member

tobrun commented Feb 16, 2018

@osana can you cherry pick this to release-boba branch? this will not be included in the merge from master to release boba in #11152

@osana osana deleted the osana-visibleregion-rotated-11137 branch February 16, 2018 16:37
@osana
Copy link
Contributor Author

osana commented Feb 16, 2018

@tobrun cherry-picked this into release boba #11226

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Android Mapbox Maps SDK for Android
Projects
None yet
Development

Successfully merging this pull request may close these issues.

LatLngBounds.contains(LatLong) can return always 'false'
2 participants