MTDirectionsKit

=1.6.1 6.2.2013
* Removed fromLocation/fromAddress & toLocation/toAddress in favor of from and to in MTDDirectionsOverlay
* Convenience method on MTDWaypoint to check if it represents the current location
* Method to determine distance between given point and active route
* New delegate call: mapView:didUpdateUserLocation:distanceToActiveRoute:ofDirectionsOverlay: that includes the distance between the user location and the active route of the directions overlay
* [MTDWaypoint coordinate] is now readonly
* [MTDWaypoint waypointForCurrentLocation] updates its coordinate property when user location gets updated
* Calling MTDOverrideClass with Nil/nil as classToUse removes a previously overridden class
* Updated UI of MTDManeuverTableViewController: displays a header/footer cell with information about departure, destination and the route
* Add - [MTDRoute containsTollRoad] property to check if a route contains toll roads (only supported for MapQuest & Bing APIs)
* Support for avoiding toll roads as well as highways when requesting directions
* New delegate call: mapView:shouldActivateRoute:ofDirectionsOverlay: to give fine-grained control whether a route can be activated by tapping on it
* New delegate call: mapView:colorForRoute:ofDirectionsOverlay: to allow different colors for each route, when alternative routes are enabled
* Support for HTTPS when requesting directions (only supported by Google and Bing API)

=1.5.0 12.10.2012
* Further improved gesture recognizer support that doesn't infere with the default gesture recognizers of MKMapView
* New delegate call mapView:didActivateRoute:ofDirectionsOverlay: that indicates when the user actives a given route
* Added function MTDDirectionsKitGetVersionString()
* NSCopying support for MTDDistance, MTDAddress and MTDWaypoint
* NS_ENUM used for all enums, now requiring Xcode 4.5
* Removed subscripting category for Xcode 4.4
* Shortcut for creating a waypoint from an address string + [MTDWaypoint waypointWithAddressString:]
* Much faster performance when parsing data from MapQuest and Bing APIs
* Support for maneuvers for all 3 APIs to allow for a textual representation of the route, with information about
- coordinate
- duration
- time
- textual instructions
- cardinal direction (except Google)
- turn type (except Google)
* Locale can be set to request maneuver description in a given language

= 1.4.0 24.9.2012
* Support for Bing Routes API
* Support for custom requests/parsers with MTDDirectionsAPIRegisterCustomRequestClass/MTDDirectionsAPIRegisterCustomParserClass
* Fixed a bug where zoomToShowRegionAnimated didn't show all routes, when alternative routes were requested
* Fully tested under iOS 6
* MTDDirectionsOpenInMapsApp works on iOS 6 and has support for [MTDWaypoint waypointForCurrentLocation]
* Added - [MTDAddress addressDictionary] - this dictionary is used when opening directions in the built-in Maps App
* Fixed a bug where address parsing didn't work when the waypoint didn't have a valid coordinate (e.g. [MTDWaypoint waypointWithAddress:])
* Fixed: Custom gesture recognizer on MapView is only enabled, when alternative directions are visible
* Fixed: Custom gesture recognizer doesn't interfere with other gesture recognizers of the MapView
* Support for armv7s, dropping support for iOS < 4.3 and armv6

* Support for Alternative Routes!
* Intermediate goals now get reordered and appear in the same order returned by the used API, if the order got optimized
* Addresses of intermediate goals now get parsed as well
* All private methods are now prefixed with "mtd_"
* Code got converted to Modern Objective-C Syntax
* Parsing now happens on a global concurrent queue
* Much more unit tests
* Google Directions now supports Transit Directions
* New Google API URL
* MTDDirectionsOverlay now has information about intermediate goals
* Better Address Parsing of the start- and end-location of a route

* Possibility to specify the thickness of the route overlay
* Turned on a lot of warnings in the compiler and make sure none of them exists in MTDirectionsKit
* Optimizing the route when providing intermediate goals is now optional
* More AppleDoc Documentation