Michael Kirk
Michael Kirk
I'm fine to follow up with a 4.0 release. I fixed https://github.com/maplibre/maplibre-navigation-ios/issues/57 in #58. Unfortunately It's not exactly a trivial fix. There were several different things critically wrong with it.
> I am wondering, isn't it possible to change this on the client side using something like this: > ```swift > for gestureRecognizer in mapView.gestureRecognizers ?? [] where gestureRecognizer is...
I think I understand how this change makes the code more mathematically "pure", but are you actually running into a problem with the current implementation? Can you succinctly describe that...
I totally forgot about this one. Sorry — we should have merged it months ago.
Pushed up some missing docs - sorry 🙇
Better documentation is always appreciated.
To make this even more confusing, I noticed HaversineBearing and GeodesicBearing return -180..180, while Rhumb returns 0..360! I'm going to take a stab at unifying this as part of #1181...
Interesting. I'm not really sure what to expect in that situation. Just thinking about it conceptually, it seems like bearing is undefined in the case of no movement. But if...
Closing the loop on this - the new line measure traits in #1216 uniformly output a bearing in 0...360. I decided to leave the legacy traits as they are (with...
Re-opening until `wkt_string` avoids intermediate allocations.