Releases: MappedIn/ios
Releases · MappedIn/ios
Release list
v1.4.3
- Fixed issue with accessible directions
v1.4.2
v1.4.1
v1.4.0
v1.3.0-beta (Febuary 21st, 2019)
Added new APIs to get all polygons, or all locations in view of the camera and look up if a specific polygon or location is in view of the camera.
// Returns a set of polygons currently in view of the camera
mapview.polygonsInView()
// Returns a set of locations that have polygons currently in view of the camera
mapView.locationsInView()
// Returns true if polygon is currently in view of the camera
mapView.isInView(polygon: polygon)
// Returns true if location has polygons currently in view of the camera
mapView.isInView(location: location)v1.2.1 (Febuary 8th, 2019)
- Bug Fix: Fixed a memory leak caused by a
Pathpulse animation.
v1.2.0 (January 29th, 2019)
-
Added support for a path pulse to the
Pathobject. ThePathpulse can be accessed as a set of options when you create thePathobject. APathpulse is a highlight that moves down the direction of the path to direct the user to the correct direction that the Path is leading them. This is identical to what is found in the Mappedin web SDK./// we can enable the Path pulse let path = Path( points: directions.path, width: 2, height: 2, color: .blue, pulseEnabled: true )
-
Fixed bug in the
Coordinate.meters(from: [Coordinate])that would report the incorrect distance if a single point was given.
v1.1.2 (November 2nd, 2018)
- Fixed problem where the map would vanish when the Camera was modified.
v1.1.1 (October 17th, 2018)
- Fixed issue where adding overlays to the MapView could cause Z-fighting
- Fixed Memory Leaks
v1.1.0 (September 18th, 2018)
- Migrated from Swift 4.1 to Swift 4.2