| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This allows us to distinguish them from other types of errors
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* [ios] Add custom delay
Adds a custom delay to the events library initialization. This is only active when using certain profile configurations.
* [ios] events library version update to v0.4.1
* Update Events Library to include missing MGL_EXPORT
* Add MMEEventsService files to Events Lib Submodule
* Change delayTime type to int64_t
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
canceled
Reverts d5aff71 (#11948) and implements an alternative solution.
Even with the previous fix applied, we were calling `renderFinished()` directly when the render was canceled. This led to the following scenario (all on the main thread):
- `Map::renderStill()` callback is called, `uv_async_send` schedules a call to `renderFinished()`.
- `NodeMap::cancel()` destroys the map object, and calls `renderFinished()` directly, which cleans up the request
- `NodeMap::startRender()` is called to schedule a _new_ render, which means that a new callback will be set
- The `uv_async_t` fires and calls `renderFinished` again:
- We don't return early as intended by the fix in #11948 since a new callback/`req` object is now available.
- Since neither error nor image has been set, we'll see a `Didn't get an image` error message.
- We call the callback with the error. In scenario where we're reusing Map objects, we will start a new render, which will now trigger the `Map is currently rendering an image` error in `Map::renderStill`, and the map object enters a circle in which it will now fail repeatedly with this error.
This commit fixes the issue by completely removing the existing `uv_async_t` handle that could have a scheduled call, and replacing it with a fresh instance of an `uv_async_t` handle.
|
| |
|
|
|
|
|
|
| |
* Change error message with invalid render usage
This change disambiguates this error condition with a different error with the same error message at https://github.com/mapbox/mapbox-gl-native/blob/789baf4c1f252071bf58e689e050b34eb2656363/src/mbgl/map/map.cpp#L157-L160
* fix test expectation
|
| |
|
|
| |
We'll have to extract the location of Xcode's developer dir from $PATH :(
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
The intention of the `WITH_CXX11ABI` option is to allow the user to control toggle whether to compile against the CXX11ABI in libstdc++ (and whether to download a few specific CXX11ABI compatible mason packages as well).
This option is important if you are building binaries (like the node binaries) and you want to support a platform that is older and does not have a recent enough libstdc++ to support the CXX11ABI (like ubuntu:precise, centos6, etc).
But this was broken for clang++ builds due to the use of `MAKE_COMPILER_IS_GNUCXX`. That was preventing the correct flags from being set when using clang++ effectively making the option useless and resulting in the build defaulting to whatever the libstdc++-dev headers default is on the system (which varies per linux distribution based on how libstdc++-dev is packaged).
This fixes the problem by ensuring that clang++ builds still support toggling control over this option.
Note: clang++ > 3.9 supports targeting both the new CXX11ABI in libstdc++ (with `-D_GLIBCXX_USE_CXX11_ABI=1`) and targeting the old one (with `-D_GLIBCXX_USE_CXX11_ABI=0`).
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* [ios, macos] Add expression support to to-rgba operator.
* [ios, macos] Update style docs.
* [ios, macos] Refactored to-rgba to to-color.
* [ios, macos] Add support for to-rgba expression operator.
* [ios, macos] Add multiple parameters support to to-color operand.
* [ios, macos] Enable to-rgba operator for MGLColor or key path expressions.
* [ios, macos] Update predicates and expressions guide to reflect cast changes.
* [ios, macos] Update changelogs.
* [ios, macos] Clarify color casting usage.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
* [ios, macos] Add support for subscripting in expressions.
* [ios, macos] Update changelogs.
* [ios, macos] Refactor LAST subscripting expression.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
* [ios, macos] Fix overlay bounds that span the antimeridian.
* [ios, macos] Update changelogs.
* [ios, macos] Make MGLLocationCoordinate2DIsValid private.
* [ios, macos] Update changelogs.
|
| |
|
|
|
|
| |
* [macos] update jazzy for macos
* [ios] moved migration guide
|
| |
|
|
| |
annotation views (when adding back into queue). (#11817)
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
MBGLOfflineRegionObserver is owned by the offline database thread, and might be destroyed by the time the dispatch_async completes. Instead of implicitly capturing this, capture a copy of the MBGLOfflinePack weak pointer.
|
| | |
|
| | |
|
| |
|
|
| |
Fixes issue #11811 (too much CPU time spent in CrossTileSymbolIndex).
|
| |
|
|
| |
Prompted by enabling CLANG_WARN_OBJC_IMPLICIT_RETAIN_SELF.
|
| |
|
|
|
| |
- Fix duplicate NSExpression+MGLAdditions.h and fix target membership
- Explicitly cast NSUInteger to unsigned long before printing
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
