| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We have an "oldBinding" value that we use for checking whether the vertex attribute was already
bound to the current VAO, but we never set the state. Additionally, we're also checking whether
the previous state was already any binding (optional is set), and don't re-enable the vertex
attribute array. Additionally, we now only disable the vertex attribute array when the previous
state was in fact an array attribute. We still don't deduplicate constant glVertexAttrib* calls,
but that's a little trickier.
|
| | |
| | |
| | |
| | | |
For #pragmas, don't generate varyings for attributes that aren't used by the fragment shader. Pack other varyings more tightly.
|
| | |
| | |
| | |
| | |
| | |
| | | |
* [core] - bump earcut version dependency to handle unused lamba warning (#9242)
* [android] - snapshot bitmap contains view based content (#9252)
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
(#9198)
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* [ios][macos] test remove source in use
* [android] test remove source in use
* [core] check source usage before remove
* [core] ensure layer::accept works with non-void return values on gcc
* [android] - remove upgrade runtime exceptions (#9191)
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
* [android] - custom location engine fixes (#9139)
* Update to latest LOST dependency, fixup internal location source integration
|
| | |
| | |
| | |
| | | |
(#9212)
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The isClose threshold is switched from 0.000001 pixels to 1 pixel.
As a backup, it checks whether r0 and r1 are finite. It might be
possible to have just the threshold check or just the finiteness check,
but I don't see the harm in having both.
std::abs(w0 - w1) < 0.000001 is removed because it doesn't look like
it's needed. All calculations should run fine even if w0 === w1.
Finally, the point interpolation is tweaked so that at the end of the
flying (when k === 1) it ends up at the exact end point. I didn't see
any bugs related to this, but it seems like a good thing to have
explicitly.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* [android] - keep location tracking mode after screen rotation (#9186)
* [android] - using easeCamera to keep location tracking instead of overloaded moveCamera (#9187)
* [android] - checkstyle fix up
|
| | | |
|
| | |
| | |
| | |
| | | |
be ignored. (#9192)
|
| | | |
|
| | |\
| | | |
| | | |
| | | | |
github.com:mapbox/mapbox-gl-native into release-ios-v3.6.0-android-v5.1.0
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This commit adds `rotatesWithMap` property on `MGLAnnotationView`. This
property, when set to `YES` fixes the annotation to a map such that view
follows map's rotation angle. This is useful when user wants to display
rotation-dependent annotations (e.g. sector lights).
|
| | |/ |
|
| | |
| | |
| | |
| | | |
exception (#9159)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* [android] Fix tracking mode + camera race condition (#9133)
* [android] fix tracking mode + camera race condition
* fix resetTrackingModesIfRequired bug (comparing current camera position with target camera position
* cherry pick #9133 and update CHANGELOG
* add null check to prevent null pointer exception
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* [android] - javadoc update for 5.1.0 release
* oxford comma
* Grammar/spelling tweaks
* grammar tweak
* grammar tweak
* Grammar tweaks
* Grammar tweaks
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* [ios, macos] Updated feedback URL
* [ios, macos] Add referrer, heading, pitch to feedback URL
* [ios, macos] Updated changelogs for feedback changes
* [ios] Vary referrer by platform
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* [android] - Changelog update for Android release v5.1.0-beta.3
* update CI & version
* reset release properties
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
* update lost to final version 3.0.0
* bump MAS version to 2.1.1
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
* [android] - Correct logo placement for creating a Mapview programatically, fixup non default placements
* Fixed NIGHTY_TWO_DP typo to NINETY_TWO_DP
|
| | | |
|
| | |
| | |
| | |
| | | |
Use a common init function in both of the provided initializers so that subclasses of `MGLAnnotationView` written in Swift don't need to override `init(annotation, reuseIdentifier)`
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Enable the View ‣ Traffic Night menu item and check it when that style is active.
|
| | | |
|
| | |
| | |
| | |
| | | |
Reorganized the changelogs with a new packaging section. Added blurbs about #9062, #8713, #9060, and #9031.
|
| | | |
|