summaryrefslogtreecommitdiff
path: root/platform
Commit message (Collapse)AuthorAgeFilesLines
* [ios] Conform to SMCalloutViewDelegateMinh Nguyễn2016-02-091-0/+9
| | | | | | #3322 #3456 replaced SMCalloutViewDelegate conformance with MGLCalloutViewDelegate conformance. Unfortunately, the two protocols differ in some symbols. This change restores SMCalloutViewDelegate methods alongside MGLCalloutViewDelegate methods. Fixes #3871.
* [ios] Load categories in MGLAccountManager for FabricMinh Nguyễn2016-02-091-0/+10
| | | | These categories need to be loaded explicitly so that they’re linked into the application binary. In the dynamic framework, they’re loaded inside the InitializeMapbox() framework initializer; for static frameworks, we recommend setting the -ObjC flag. Fabric uses the static framework without setting the -ObjC flag, so these redundant calls are needed.
* [android] #3830 added mocked parcel implementationTobrun2016-02-052-0/+189
|
* Fix Memory leak caused by duplicated add in LocationListener listjaumeolba2016-02-051-1/+3
| | | | | | | | | | | | | The addLocationListener method didn't check if the LocationListener was already in the list. From MapView, if we call setMyLocationEnabled(true), it adds a LocationListener and onResume adds the same LocationListener again, but is just removed by onPause. So LocationListener is added twice but removed just once, so LocationServices singleton keeps an instance of the the LocationListener that is never released.
* node-v3.0.2node-v3.0.2Mike Morris2016-02-041-0/+6
|
* [node] patch memory leak in NodeMap::requestMike Morris2016-02-041-1/+1
| | | | | | | | Creating a v8::Function with Nan::GetFunction(Nan::New<v8::FunctionTemplate>) can leak, use Nan::New<v8::Function> instead. https://code.google.com/p/chromium/issues/detail?id=272579
* [ios] Explain prerelease testing in docsJordan Moncharmont2016-02-041-1/+10
| | | Show how to point a podspec at an officially tagged pre-release.
* [core] Remove Response::Error::Reason::CanceledJohn Firebaugh2016-02-042-4/+5
| | | | There is no such thing as a cancelled response, only cancelled requests. A request that is cancelled does not have its callback called with a Response.
* [all] Make #include <mapbox/variant.hpp> universally accessibleJohn Firebaugh2016-02-042-2/+0
|
* [android] #3811 - handle null target value by using previous camera position.Tobrun2016-02-041-0/+9
|
* [android] #3758 - Projection / Visible Region implementation.Tobrun2016-02-0424-686/+460
| | | | [android] #3758 - add VisibleRegion + unit tests, removed boundingbox, cleanup jni, cleanup test app, renamed CoordinateSpan to LatLng.
* [android][core] #509 - Setting Min and Max Zooms warning annotations in ↵Brad Leege2016-02-031-2/+2
| | | | Android. Clamping Min and Max zooms at Core GL for all platforms to use at runtime.
* [ios] Fixed designable warning when showing user locationMinh Nguyễn2016-02-031-1/+1
| | | | Turn the Shows User Location inspectable into a no-op when running in the designables agent. Otherwise, we complain that the agent lacks Location Services permissions.
* [android] #3752 - added scroll by x,y feature, introduced new ↵Tobrun2016-02-0311-42/+422
| | | | | | CameraUpdateType, introduced caching system for invalidating CameraPosition, general cleanup, readded getLatLng in MapView, .. [android] #3752 - correctly invalidating cameraposition
* [core] Improve LatLngBounds APIJohn Firebaugh2016-02-025-43/+37
| | | | | | | * Use "named constructors": empty, world, hull * Make the two-argument constructor lenient (i.e., it is a hull operation) * Add various accessors * Enforce a single empty representation
* [android] #3736 - clicks should ignore marker validation when an ↵Tobrun2016-02-021-1/+1
| | | | InfoWindowAdapter is supplied by end developer.
* [android] #3754 - newLatLngBounds: unit tests for LatLng and LatLngBounds, ↵Tobrun2016-02-0234-768/+690
| | | | | | | | | | builder pattern + refactoring. [android] #3754 - Working version using the underlying VisibleCoorindateBounds [android] #3754 - refactor Camera api inside maps package, correctly use factory pattern, LatLngBounds hooks into camera API [android] #3754 - cleanup old API
* [android] #3759 - Add SupportMapFragment, test app integration, cleanup old ↵Tobrun2016-02-029-27/+201
| | | | fragment implementation
* [ios] Renamed -showAnnotations:withEdgeInsets:animated:Minh Nguyễn2016-02-011-5/+3
| | | | Renamed -showAnnotations:withEdgeInsets:animated: to -showAnnotations:edgePadding:animated: for consistency with other methods. Reworded documentation comments to avoid hard-coding too many specifics that are prone to getting outdated.
* Custom edgeInsets for fitting in showAnnotationsJordan Moncharmont2016-02-011-5/+14
| | | | Keeps sensible defaults already in place, but allows callers to override.
* [android] #3776 - UiSettings uses MapView instead of MapboxMap as ↵Tobrun2016-02-016-191/+118
| | | | dependency. Cleanup obsolete methods MapboxMap/MapView, Renaming convention Google Maps SDK, Update tests, Some minor fixes in state management
* [android] #3753 - Optimising zoomTobrun2016-02-015-127/+309
| | | | [android] #3753 - removed old zoom methods from MapView
* [android] #3760 - parity with Google Maps SDKTobrun2016-02-0111-464/+819
| | | | | | [android] #3760 - added missing methods for UiSettings, updated tests and test app to reflect this change [android] #3760 - typo fix
* [android] #3145 - MapboxMapTobrun2016-01-2987-3030/+4580
|
* [ios] Removed redundant usage sectionMinh Nguyễn2016-01-281-5/+19
| | | Also copied some further setup steps from the IB page on the project wiki.
* [ios] Restored toggleDebugMinh Nguyễn2016-01-281-5/+5
| | | | Restored (but deprecated) a method removed in #3100 to avoid a major version bump.
* [ios] Debug maskMinh Nguyễn2016-01-281-7/+50
| | | | Ported MGLMapDebugMaskOptions from the OS X SDK. Deprecated debugActive and -cycleDebugOptions.
* [ios] Eliminated “flashlight mode”Minh Nguyễn2016-01-281-2/+9
| | | | | | Avoid resetting user tracking state when going from location or course tracking mode to heading tracking mode. Fixes #3710.
* [osx] setMaximumZoomLevel, setMinimumZoomLevelAnsis Brammanis2016-01-281-0/+10
| | | | | | | | adds: setMaximumZoomLevel setMinimumZoomLevel and makes `maximumZoomLevel` and `minimumZoomLevel` not readonly
* [ios] getters, setters for minZoom, maxZoomAnsis Brammanis2016-01-281-0/+20
| | | | | | | | adds: minimumZoomLevel setMinimumZoomLevel maximumZoomLevel setMaximumZoomLevel
* [android] getters, setters for minZoom, maxZoomAnsis Brammanis2016-01-283-0/+82
| | | | | | | | adds: map.getMminZoom(); map.setMminZoom(double); map.getMaxZoom(); map.setMaxZoom(double);
* [android] #3716 - Setting Android Version to 4.0.0-SNAPSHOTBrad Leege2016-01-281-1/+1
|
* Merge branch 'master' into release-android-v3.2.0Brad Leege2016-01-282-1/+12
|\
| * [android] #3728 - Adding Back Pressed support for App Bar Home ButtonBrad Leege2016-01-281-0/+11
| |
| * [ios] Remove dependency on variable in package.shMinh Nguyễn2016-01-281-1/+1
| | | | | | Fixes #3725.
* | [android] #3716 - Updating version to 3.2.0 for releaseBrad Leege2016-01-282-2/+2
| |
* | [android] #3723 - Commenting out content padding in MapView APIBrad Leege2016-01-281-1/+12
| |
* | [android] #3692 - fix crash with bad internet connectionTobrun2016-01-281-1/+3
|/
* [android] #3708 - added code coverage test documentation and debug optionTobrun2016-01-283-2/+33
|
* [ios] Remove incorrect tab whitespace in methodJesse Bounds2016-01-271-19/+17
| | | | | | | | | | | This just removes some whitespace that made the implementation of `pushTurnstileEvent` in `MGLMapboxEvents` look a little strange. The indentation was right below an early return conditional (with no braces) so it felt like the right thing to do (for readability) to clean it up. Choosing and enforcing a consistent style for conditionals with one line might be a good idea, too, but this small change does not go there.
* [android] Add getters for content paddings.Larry Geromegnace2016-01-271-0/+33
|
* [android] Use padding to get center coordinates.Larry Geromegnace2016-01-272-2/+2
|
* [android] Add API to be able to set insets on MapView.Larry Geromegnace2016-01-275-1/+63
|
* [ios] Update location after clearing target coordinateMinh Nguyễn2016-01-261-8/+12
|
* [core, ios, osx] Tilt around visual center pointMinh Nguyễn2016-01-263-5/+11
| | | | The tilt gesture on both iOS and OS X now respects the content insets. On iOS, in user tracking mode, it additionally respects the user dot’s position if it’s aligned to the top or bottom of the view.
* [ios] Fixed entering tracking mode at launchMinh Nguyễn2016-01-262-23/+35
| | | | | | Entering user tracking mode at launch now zooms in and shows the user dot or user puck. The user dot’s heading indicator now points in the correct direction during the animation to the initial location. Course changes are reflected immediately even in the absence of location changes. Fixes #1145.
* [ios] Refactored location updatesMinh Nguyễn2016-01-261-145/+174
| | | | | | Broke out -locationManager:didUpdateLocations:animated: into multiple self-contained methods, simplifying the logic considerably. Eliminated a jump after device rotation in non-centered tracking mode.
* [ios] Bifocal viewport in course tracking modeMinh Nguyễn2016-01-262-30/+125
| | | | When a targetCoordinate is specified in course tracking mode, the map automatically resizes the viewport to show both the user puck and the target, one at the top and the other at the bottom. The user puck now rotates its arrow in the course direction, no longer assuming that the viewport is facing the same way as the course.
* [ios] Turn map around when user dot is top-alignedMinh Nguyễn2016-01-261-4/+9
| | | | Also fixed top- and bottom-aligned user dot center points to account for the content inset’s offset within the map view bounds.
* [ios] Avoid jumping when setting user tracking modeMinh Nguyễn2016-01-261-24/+42
| | | | | | | | Account for the user dot’s alignment when flying to the initial user location. Previously, during incremental location updates, we relied on a hack in which the edge insets resulted in a 0×0 viewport, forcing the center upward or downward. But flyTo() relies on the viewport’s size to control the trajectory. So instead, all location updates now use a correctly-sized viewport centered on the offset user dot. Pushed the user dot farther away from the view edges. Programmatic rotation and compass rotation are now centered on the user dot even if it’s aligned at the top or bottom. Previously, pressing the compass would trigger a rotation centered on the center of the view.