| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
If a workRequest exists, don't cancel it and start an new request. It's
ok to just do nothing if the request exists because a new call to
redoPlacement will be triggered after the existing request finishes.
this fixes a regression in e44db93f1cb3276dcdc7de8400ca96beda1b1d30
|
| |
|
|
|
|
|
|
|
|
| |
We switched to libjpeg-turbo in #3632.
Original license requirements: https://github.com/libjpeg-turbo/libjpeg-turbo/blob/master/LICENSE.md
License: https://github.com/libjpeg-turbo/libjpeg-turbo/blob/master/turbojpeg.c
[skipci]
|
| | |
|
| |
|
| |
Also copied some further setup steps from the IB page on the project wiki.
|
| |
|
|
| |
Restored (but deprecated) a method removed in #3100 to avoid a major version bump.
|
| |
|
|
| |
Ported MGLMapDebugMaskOptions from the OS X SDK. Deprecated debugActive and -cycleDebugOptions.
|
| |
|
|
|
|
| |
Avoid resetting user tracking state when going from location or course tracking mode to heading tracking mode.
Fixes #3710.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
adds:
setMaximumZoomLevel
setMinimumZoomLevel
and makes `maximumZoomLevel` and `minimumZoomLevel` not readonly
|
| |
|
|
|
|
|
|
| |
adds:
minimumZoomLevel
setMinimumZoomLevel
maximumZoomLevel
setMaximumZoomLevel
|
| |
|
|
|
|
|
|
| |
adds:
map.getMminZoom();
map.setMminZoom(double);
map.getMaxZoom();
map.setMaxZoom(double);
|
| |
|
|
| |
also change the default maxZoom to 20 to match -js.
|
| | |
|
| |\ |
|
| | | |
|
| | |
| |
| | |
Fixes #3725.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
This just removes some whitespace that made the implementation of
`pushTurnstileEvent` in `MGLMapboxEvents` look a little strange.
The indentation was right below an early return conditional
(with no braces) so it felt like the right thing to do (for
readability) to clean it up. Choosing and enforcing a consistent style
for conditionals with one line might be a good idea, too, but this
small change does not go there.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
The tilt gesture on both iOS and OS X now respects the content insets. On iOS, in user tracking mode, it additionally respects the user dot’s position if it’s aligned to the top or bottom of the view.
|
| |
|
|
|
|
| |
Entering user tracking mode at launch now zooms in and shows the user dot or user puck. The user dot’s heading indicator now points in the correct direction during the animation to the initial location. Course changes are reflected immediately even in the absence of location changes.
Fixes #1145.
|
| |
|
|
|
|
| |
Broke out -locationManager:didUpdateLocations:animated: into multiple self-contained methods, simplifying the logic considerably.
Eliminated a jump after device rotation in non-centered tracking mode.
|
| |
|
|
| |
When a targetCoordinate is specified in course tracking mode, the map automatically resizes the viewport to show both the user puck and the target, one at the top and the other at the bottom. The user puck now rotates its arrow in the course direction, no longer assuming that the viewport is facing the same way as the course.
|
| |
|
|
| |
Also fixed top- and bottom-aligned user dot center points to account for the content inset’s offset within the map view bounds.
|
| |
|
|
|
|
|
|
| |
Account for the user dot’s alignment when flying to the initial user location. Previously, during incremental location updates, we relied on a hack in which the edge insets resulted in a 0×0 viewport, forcing the center upward or downward. But flyTo() relies on the viewport’s size to control the trajectory. So instead, all location updates now use a correctly-sized viewport centered on the offset user dot.
Pushed the user dot farther away from the view edges.
Programmatic rotation and compass rotation are now centered on the user dot even if it’s aligned at the top or bottom. Previously, pressing the compass would trigger a rotation centered on the center of the view.
|
| |
|
|
|
|
|
|
|
|
| |
Setting the user tracking mode without animation now works. Previously, it kept the user dot from ever updating.
Just as a zoom gesture no longer kicks the user out of user tracking mode, programmatically zooming shouldn’t either.
Setting a camera with an invalid center coordinate no longer attempts to change the center coordinate but still changes any other valid properties.
Made animation to new user dot vertical alignment optional.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Apps with `whenInUse` location permission will show a blue status bar
when they continue to use location services after leaving the
foreground. This is worrying and to be avoided, so let's disable telemetry
location services in this situation.
Fixes #2945
|
| |
|
|
| |
Use mbgl::Duration and mbgl::{,Milli}Seconds whenever possible.
|
| |
|
|
| |
https://github.com/mapbox/mapbox-gl-native/issues/3159#issuecomment-174422048
|
| | |
|
| |
|
|
| |
Fixes #3300.
|
| |
|
|
|
|
| |
Settings.bundle is no longer a requirement to get started.
[skipci]
|
| |
|
|
| |
This allows the FileSource interface itself to support revalidation. We could (and probably should) now rewrite HTTPContextBase implementations as FileSource implementations.
|
| | |
|
| | |
|
