* [android] fix tracking mode + camera race condition
* fix resetTrackingModesIfRequired bug (comparing current camera position with target camera position
* Add `overlays` property to `MGLMapView.mm`
Implemented by filtering the `annotations` property for
annotations that conform to `MGLOverlay` protocol.
* Handle `nil` case when returning overlays
* Add basic documentation for `overlays` property
Copied verbatim from `annotations` property. Changed types.
* Add `overlays` property to iOS sdk
Implementation is identical to the one in macOS SDK.
* Match curly braces style
* Make `overlays` property `nonnull` on iOS
* Make `overlays` property `nonnull` on macOS
* Make cosmetic changes
* [ios, macos] Moved changelog entry to master
The Styles API section of the Mapbox API Documentation site now lists Traffic Day v2 and Traffic Night v2, so this change adds those styles to all the places where styles are listed.
Also switched iosapp and macosapp to unversioned style factory methods since MGLStyleDefaultVersion is no longer applicable for all styles.
Undeprecated the unversioned style URL factory methods in MGLStyle for consistency with the Android and Qt SDKs. Added warnings about using them with the runtime styling API.
Refactored mbgl::util::default_styles to track different versions for different styles.
Upgraded from v9 default styles to v10 wherever the developer expects to get the latest and greatest, as well as in a couple tests where it may be beneficial to ensure that we can handle a two-digit version number in the style URL.
* [ios] Use map view frame to calculate annotation view reuse adjustments
The value for determining the visible viewport buffer and also the distance to move offscreen an annotation view outside of that buffer was based on the annotation view width and height. This changes that to use the map viewport width and height as constants and avoids a class of bugs where the annotation view would become detached from the tracking system when it did not have a size or was animating from a small to large size.
* [ios] Use map view frame to calculate annotation view reuse adjustments
The value for determining the visible viewport buffer and also the distance to move offscreen an annotation view outside of that buffer was based on the annotation view width and height. This changes that to use the map viewport width and height as constants and avoids a class of bugs where the annotation view would become detached from the tracking system when it did not have a size or was animating from a small to large size.
