| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
interop
|
| |
|
|
|
|
| |
an invalid token
|
| |
|
|
|
|
| |
devices
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#14862)
* Change default CJK font from "PingFang" to "Helvetica"
* Add CHANGELOG.
* Update CHANGELOG.
* [ios] Enable client-side rendering and use `Helvetica` by default. Set `MGLIdeographicFontFamilyName` to `NULL` for using your custom remote font.
* [ios] Update change log
* [ios] Change default CJK configuration in `iosapp` project
* [ios] Update comment
* [ios] return local font name using default system font.
* [ios] Update changelog
* [ios] update changelogs & comments
* [iOS, macOS]Support mac os
* [iOS, macOS] fix bug
* [iOS, macOS] update change log
* [iOS, macOS] fix nit.
* [iOS, macOS] Ability to specify an array of fonts for fallbacks for `localIdeographicFontFamily`
* [iOS, macOS] Update comments
* [iOS, macOS] Update change log
* [iOS, macOS] update for mac OS font family names
* Fix nit.
* Update platform/ios/CHANGELOG.md
Co-Authored-By: Minh Nguyễn <mxn@1ec5.org>
* [iOS, macOS] Set `MGLIdeographicFontFamilyName` to a Boolean value `NO` for using your custom remote font.
* [iOS, macOS] remove `MGLIdeographicFontFamilyName` from info.plist & update Info.plist Keys.md
* [iOS, macOS] remove `MGLIdeographicFontFamilyName` from macOS demo app project and update info.plist Keys.md
* [iOS, macOS] update macOS changelog
* [iOS, macOS] Change docs
* Update Change log
* [iOS, macOS] Test case
* Update platform/macos/docs/guides/Info.plist Keys.md
Co-Authored-By: Jason Wray <friedbunny@users.noreply.github.com>
* Update platform/macos/docs/guides/Info.plist Keys.md
Co-Authored-By: Jason Wray <friedbunny@users.noreply.github.com>
* Update platform/ios/CHANGELOG.md
Co-Authored-By: Jason Wray <friedbunny@users.noreply.github.com>
* Update platform/darwin/src/MGLRendererConfiguration.mm
Co-Authored-By: Jason Wray <friedbunny@users.noreply.github.com>
* Update platform/darwin/test/MGLRendererConfigurationTests.mm
Co-Authored-By: Jason Wray <friedbunny@users.noreply.github.com>
* Update platform/macos/docs/guides/Info.plist Keys.md
Co-Authored-By: Jason Wray <friedbunny@users.noreply.github.com>
* Update platform/macos/docs/guides/Info.plist Keys.md
Co-Authored-By: Jason Wray <friedbunny@users.noreply.github.com>
* Update platform/macos/docs/guides/Info.plist Keys.md
Co-Authored-By: Jason Wray <friedbunny@users.noreply.github.com>
* [iOS, macOS] update comments
* [iOS, macOS] add plist value test && filter for invalid string
* [iOS, macOS] fix nit
* Update platform/ios/docs/guides/Info.plist Keys.md
Co-Authored-By: Jason Wray <friedbunny@users.noreply.github.com>
* Update platform/ios/docs/guides/Info.plist Keys.md
Co-Authored-By: Jason Wray <friedbunny@users.noreply.github.com>
* Update platform/ios/docs/guides/Info.plist Keys.md
Co-Authored-By: Jason Wray <friedbunny@users.noreply.github.com>
* Update platform/macos/CHANGELOG.md
Co-Authored-By: Jason Wray <friedbunny@users.noreply.github.com>
* Update platform/ios/docs/guides/Info.plist Keys.md
Co-Authored-By: Jason Wray <friedbunny@users.noreply.github.com>
* Update platform/ios/docs/guides/Info.plist Keys.md
Co-Authored-By: Jason Wray <friedbunny@users.noreply.github.com>
* [iOS, macOS] add invalid value type test
* Apply own suggestions from code review
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes following issues:
* Fix some false passing combinations/fill-extrusion-translucent--XXXX tests
* Fix and enable other, failing but ignored, combinations/fill-extrusion-translucent--XXXX tests
* Fix rendering of layers that are on top of fill-extrusion layers
state.getProjMatrix(nearClippedProjMatrix, 100) caused that tests with size 64x64 were not
rendering fill extrusions: far plane calculated as 96.9 and near plane set to 100 was the cause.
near plane is changed from hardcoded 100 to depend on state.getCameraToCenterDistance() - producing
similar value but one that follows max zoom.
This caused that e.g. combinations/fill-extrusion-translucent--fill-opaque was falsely passing as
only fill-opaque layer got rendered.
combinations/fill-extrusion-translucent--XXXX tests expose regression https://github.com/mapbox/mapbox-gl-native/issues/14844#issuecomment-503600034 in #14844, #14779.
Fix (opaquePassCutoff, is3D) is ported from https://github.com/mapbox/mapbox-gl-js/pull/7821
Fixes: #14844, #14779, #15039
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
* [ios] Add shoulRremoveStyleImage to MGLMapViewDelegate.
* [ios] Changelog update.
* [ios, macos] Update shouldRemoveStyle method documentation.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Versions had a period instead of a dash between the numbers and pre-release string.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
* Fixes problems associated with node 10 and NAN
* Follow up removal of unnecessary linking to map object
* Remove header left over from debugging
|
| |
|
| |
|
|
|
| |
In the deconstructor of run_loop.cpp there is an assert that checks to make sure the Scheduler is null before setting it to null. In some rare scenarios where the app is being put into the background or closed the Scheduler can be null before the deconsturctor is called. This can cause an unnecessary crash. Since the goal here is to just set the Scheduler to null either way, it should not matter what the state of the Scheduler is before the function call.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
behavior (#14924)
|
| |
|
| |
|
| |
|
| |
|
| |
|