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 contentInset set, if you tell the map to set the visible coordinate bounds to the current visible coordinate bounds the map moves since getting the visible coordinate bounds doesn't take into account the map content inset but setting it does
With contentInset set, if you tell the map to set the visible coordinate bounds to the current visible coordinate bounds the map moves since getting the visible coordinate bounds doesn't take into account the map content inset but setting it does
Get:
mapbox-gl-native/platform/ios/src/MGLMapView.mm
Line 3275 in 5733440
Set:
mapbox-gl-native/platform/ios/src/MGLMapView.mm
Lines 3378 to 3379 in 5733440
Steps to reproduce
Expected behavior
Get visible coordinate bounds would take into account content inset and the map would stay put
Corrected Get:
return [self convertRect:self.bounds.inset(by: self.contentInset) toCoordinateBoundsFromView:self];
Actual behavior
Map jumps to different region
Configuration
Mapbox SDK versions: ios-v4.9.0
iOS/macOS versions: iOS 12.1.4
Device/simulator models: iPhoneX
Xcode version: 10.1
The text was updated successfully, but these errors were encountered: