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

Smallest LatLngBounds when visible region crosses dateline #9747

Merged
merged 1 commit into from
Aug 17, 2017

Conversation

tobrun
Copy link
Member

@tobrun tobrun commented Aug 10, 2017

closes #9687, this PR makes sure that the LatLngBounds returned by VisibleRegion complies to:

The smallest bounding box that includes the visible region defined in this class.

To make this possible I had to introduce LatLngBounds.from, this method was required to bypass bounds recalculation used in normal circumstances. This method also allows end developers to overwrite default LatLngBounds behaviour.

Adding this to the 5.1.3 milestone as implementation wasn't complying to the javadoc.

cc @zugaldia

@tobrun tobrun added the Android Mapbox Maps SDK for Android label Aug 10, 2017
@tobrun tobrun added this to the android-v5.1.3 milestone Aug 10, 2017
@tobrun tobrun self-assigned this Aug 10, 2017
@tobrun tobrun force-pushed the tvn-fix-visible-bounds-dateline branch from 046167e to 4782048 Compare August 10, 2017 13:25
@tobrun tobrun force-pushed the tvn-fix-visible-bounds-dateline branch from 4782048 to ba00d25 Compare August 10, 2017 16:55
Copy link
Contributor

@Guardiola31337 Guardiola31337 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me although Firebase is complaining 😞

@tobrun tobrun merged commit 830bf15 into master Aug 17, 2017
@tobrun tobrun deleted the tvn-fix-visible-bounds-dateline branch August 17, 2017 14:48
@tobrun tobrun mentioned this pull request Aug 18, 2017
19 tasks
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 and the international dateline
2 participants