| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Add changelog PR link
|
| |
|
|
|
|
| |
Binary shader support has been removed in commit c2f974f2a573 ([core]
Remove binary shader support). This left-over parameter is not used
anywhere anymore.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* [ios] Improve tilt gesture recognizer detection.
* [ios] Update tilt gesture detection angles.
* [ios] Fix a delay at the beginning of the drag gesture.
* [ios] Update tilt gesture recognizer tests.
* [ios] Update changelog.
* [ios] Add horizontal tilt gesture test.
* [ios] Addresses review feedback.
* [ios] Add comments to clarify the tilt gesture initialization.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
(#15123)
|
| |
|
|
|
|
| |
* [ios] document scale bar visibility
* [ios] finished trailing sentence
|
| |
|
|
|
|
|
|
| |
* map id --> tileset id
* styles map id -> style url
* update changelog
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To changelog:
Fixed incorrect center coordinate after pinch regression caused by edge insets fix (#14664).
While working on #14664, missed to understand the logic used in
```
CLLocationCoordinate2D centerCoordinate = _previousPinchCenterCoordinate;
mbgl::EdgeInsets padding { centerPoint.y, centerPoint.x, self.size.height - centerPoint.y, self.size.width - centerPoint.x };
self.mbglMap.jumpTo(mbgl::CameraOptions()
.withCenter(MGLLatLngFromLocationCoordinate2D(centerCoordinate))
.withPadding(padding));
```
Replacing this code by moveBy achieves the required translation.
Fixes: #14977, #15082
|
| | |
|
| |
|
|
|
|
|
|
| |
* [ios] Add shoulRremoveStyleImage to MGLMapViewDelegate.
* [ios] Changelog update.
* [ios, macos] Update shouldRemoveStyle method documentation.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
* [ios] Mapbox Events 0.9.4
* Run `scripts/generate-file-lists.js`
* Explicitly use the shared manager instead of init
* There can be only one `Scripts`
|
| |
|
|
|
| |
* Use a stringy selector... yerg.
* Bump to libmbxaccounts 1.0.0
|
| | |
|
| |
|
|
| |
Fixes: #14807
|
| |
|
|
| |
`setCoordinate:` isn't available to regular MGLAnnotation, only MGLPointAnnotation.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* [ios] Fix content insets with custom edge padding.
* [ios, macos] Consolidated edge insets math
* [macos] Add content insets to edge padding when setting camera
* [ios, macos] Updated changelogs
* [ios, macos] Clarify setCamera:withDuration:animationTimingFunction:edgePadding method documentation.
|
| |
|
|
|
|
|
|
| |
Allows changing camera when user duplicates content insets.
Related to previous patch and comment:
https://github.com/mapbox/mapbox-gl-native/pull/14664#pullrequestreview-243004376
Thanks @1ec5
|
| | |
|
| |
|
|
| |
Check edge insets difference, in addition to isEqualToMapCamera in all the places in MGLMapView before map.easeTo/map.flyTo.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The change is implemented in TransformState::getProjMatrix, the rest of the code is making sure that existing API contracts stay and there are tests verifyingrendering and render query processing only items within screen and given tolerance around screen edges.
MapView: don't bake edge insets into relalculated camera center. Keep edge insets as property of camera in TransformState (similar to pitch, zoom, bearing) independent from specified camera center. Interpolate edge insets in animation.
iOS Demo app: "Turn On/Off Content Insets" pitch the camera and navigate to convenient location in Denver, where streets are parallel to cardinal directions, to illustrate viewport center offset when edge insets are set.
Tests:
ViewFrustumCulling: although Annotations are deprecated, queryRenderedFeatures related tests in Annotations would need to get ported and decided to add the edge insets related query tests next to them. Verify frustum culling (render+queryRenderedFeatures) With different camera and edge insets setups. TODO: port Annotations tests.
Transform.Padding: Verify that coordinates take proper place on screen after applying edge insets.
LocalGlyphRasterizer: verify text rendering when applying padding.
Related to #11882: both use projection matrix elements [8] and [9].
Alternative approach to this was to increase and offset map origin so that the screen would be a sub-rectangle in larger map viewport. This approach has a drawback of unecessary processing the items that are outside screen area.
Fixes #12107, #12728, navigation-sdks/issues/120
|
| |
|
| |
Removes conditional code that relied on a plist flag. Other small cleanups.
|
| | |
|
| |
|
|
|
|
|
|
| |
shouldChangeFromCamera delegate (#14680)
* [ios, macos] clarified documentation for newCamera in shouldChangeFromCamera
* [ios, macos] clarified documentation for newCamera param of the shouldChangeFromCamera delegate part 2
|
| |
|
|
|
|
|
|
|
|
| |
- Do not carry it over everywhere as parameter, it is a shared
instance anyway and the lifecycle is pretty much the app lifecycle
from the moment we instantiate a map.
- Rename to BackgroundScheduler because it is a Scheduler that will
do tasks in the background, we don't make assumptions if it is a
thread pool or a single thread.
- Most importantly, remove the dependency from `core` on `platform`.
|
| | |
|
| |
|
|
|
|
|
|
| |
coordinates (#14575)
* [ios] Fixed negative direction when setting visible coordinates
* [ios] Document behavior of negative direction
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
presentsWithTransaction (#14445)
|
| |
|
|
| |
rendering in the background (#14439)
|
| |
|
|
| |
Fixes https://github.com/mapbox/mapbox-gl-native/issues/14329
|
| |
|
|
| |
background (#14383)
|
