This changes image size properties to be scales instead of pixel sizes.
The commit also adds fixes for handling image updates with the same ID,
adds tests for expressions in paint properties, as well as tests for using images
with pixel ratio greater than 1.
Finally it moves image-tilt-displacement and perspective-compensation properties
from layout to paint properties, and includes other minor cleanups.
* [build] Fix integer overflow runtime error for core part
Temporarily remove circle ci UBSAN build precondition
* [build] Enable all of the ubsans
[build] Check runtime error
[build] Update UBSAN_OPTION
* [build] Add UBSAN blacklist
[build] Ignore system libraries
[build] Ignore vendor library
* [build] Fix implicit conversion runtime error in core
* [build] Fix division by zero runtime error
* [build] Add unfixed error to ubsan blacklist
* [build] Make UBSAN halt on error
Revert "Temporary remove build precondition"
* [build] Fix division by zero error
* [build] Make UBSAN officially work without FIXME prefix
* [build] Fix implicit conversion from int64_t to uint64_t
* [build] Rename style test json file name
* Address review findings
* [android] Add jni binding for styleable snapshotter
* Remove Map parameter from factories
- remove unused map from factory interfaces. Map is only needed for repaint.
* implement addlayer function
* Implement addsource function for snapshotter
* Implement addImages function
* format codes
* Apply baseline
* Update CHANGELOG.md
* Update map_snapshotter.cpp
* Destroy snapshotter on the thread it was created
* Activate file sources in start
* Use custom deleter for snapshotter
* format codes
* Release snapshotter pointer to deleting lambda
* Clang format
* Update CHANGELOG.md
* Fix review comments
* FIx review comments
Co-authored-by: Alexander Shalamov <alexander.shalamov@mapbox.com>
Use the same test manifest for the development and nightly
coverage CI builds. Add manifest for the nightly build by
creating a symbolic link to the existing manifest.
This change fixes the following problems:
1) Before this change, when multiple symbols were grouped close to the
tile borders, different tiles could place different symbols, because each
tile arbitrary assigned feature ids, and these ids defined the placement
order being applied. This caused artifacts at the tile boundaries.
With this change, in tile mode the placement order of two symbols crossing
a tile border is defined by their anchor `y` values. It means that the
symbols are being placed the same order across all the tiles.
2) Before this change, the engine did not place with priority the symbols
crossing the borders between two neighboring tiles. Now it does, and it
improves a lot symbol placement stability in the tile map mode.
