| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Previously we had the capability to pause on the Thread object, which used regular tasks to pause the RunLoop by blocking it. Instead, we can now pause the entire RunLoop and prevent it from processing items. This means that a pause() call is no longer treated as a regular task. Instead, it will take precedence over scheduled tasks, which means that a pause() call takes effect much more instantly since the RunLoop doesn't process the queue before the pause() task. Having pause() take effect much quicker is useful for situations where stopping the loop quickly is important, e.g. when the application goes to the background on iOS, and we have to stop processing tasks that access the file system. It also reduces the length of the blocking pause() call since the time until the RunLoop is paused is shortened.
|
|
|
|
| |
RunLoop already has a queue, and has the ability to schedule weak mailboxes, so we can remove the duplicate code.
|
|
|
|
| |
cameraThatFitsShape:shape direction: edgePadding:]
|
|
|
|
| |
macOS, also added -[MGLMapView setCamera: withDuration: animationTimingFunction: edgePadding: completionHandler:] for parity with iOS
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* [ios, macos] Improve snap shotter documentation.
* [macos] Save snapshots in correct format
* [macos] Renamed snapshot item to Export Image
* [ios, macos] Clarify Snapshotter documentation.
* [ios] Fix snapshot scale
* [macOS] Fix snapshotter 4x scaling.
* [ios] Fix snapshotter final image scale.
* [ios, macos] Update snapshotter size documentation.
* [ios, macos] Throw an exception when the snapshotter has already started.
* [ios, macos] Add snapshotter header example.
* [ios, macos] Use one of the predefined Foundation's exception names.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
We don't want to link it into the node bindings, so keep it in a separate target
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
# Conflicts:
# circle.yml
# platform/android/CHANGELOG.md
# platform/android/MapboxGLAndroidSDK/gradle.properties
# platform/android/MapboxGLAndroidSDK/src/main/java/com/mapbox/mapboxsdk/maps/AnnotationManager.java
# platform/android/MapboxGLAndroidSDK/src/main/java/com/mapbox/mapboxsdk/maps/MapView.java
# platform/android/dependencies.gradle
# platform/default/mbgl/storage/offline_database.cpp
# platform/ios/CHANGELOG.md
# platform/ios/Mapbox-iOS-SDK-nightly-dynamic.podspec
# platform/ios/Mapbox-iOS-SDK-symbols.podspec
# platform/ios/Mapbox-iOS-SDK.podspec
# platform/ios/app/Main.storyboard
# platform/ios/src/MGLMapView.mm
# src/mbgl/programs/attributes.hpp
# src/mbgl/renderer/painter_fill.cpp
# src/mbgl/tile/geometry_tile.hpp
# src/mbgl/tile/geometry_tile_worker.cpp
# src/mbgl/tile/raster_tile.cpp
# src/mbgl/tile/raster_tile.hpp
# src/mbgl/tile/raster_tile_worker.cpp
# test/tile/annotation_tile.test.cpp
# test/tile/geojson_tile.test.cpp
# test/tile/raster_tile.test.cpp
# test/tile/vector_tile.test.cpp
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
required resources match and the download state is inactive) (#9913)
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Requests to servers which run on localhost should be independent from internet connection.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Updated Catalan, Spanish, Swedish, Traditional Chinese, Ukrainian, and Vietnamese.
|
| |
| |
| |
| |
| |
| | |
operations completed
Previously, when we started a worker operation that eventually throws an exception (e.g. due to the tile not being parseable), and then enqueue another worker operation while the first one is processing, we treated the worker as idle once the first operation's error callback fired, even though the second operation was still in progress. Due to our use of coalescing, I was unable to come up with a reliable test since we'd need to reproduce the behavior described above, which is timing dependent.
|
| |
| |
| |
| | |
Since 9a9408e8111bcdcd0fcb9a93112d61ab8fce0601, we marked tiles as non-renderable if an error occured. This lead to situations where a tile was loaded + parsed successfully, then a revalidation attempt occured (e.g. because the resource was stale) which failed. In this case, we used to mark the tile as non-renderable although we could've used the perfectly parsed (stale) resource.
|
| |
| |
| |
| |
| |
| | |
Otherwise it errors with, "cannot initialize a variable of type 'BOOL' (aka 'signed char') with an rvalue of type 'id _Nullable'."
This doesn't seem like it should be necessary.
|
| |
| |
| |
| |
| |
| | |
* [ios] Update changelog missing entry
* [ios] Bump podspec to 3.6.3
|
| |
| |
| |
| |
| |
| |
| |
| | |
* [ios, macos] Deprecate trafficDayStyleURL and trafficNightStyleURL
* [ios, macos] Update changelogs.
* [ios, macos] Update trafficDayStyleURL and trafficNightStyleURL tests in MGLStyleTests.
|