thanks heaps - I'll try this shortly..... Couple of quick questions if I may:
a) Is the new WWDC2013 "@Observable" approach I was trying to use not quite able to handle this by the way, re why you've had to go to ObservableObject?
b) In terms of moving to SwiftUI, then should SwiftUI "Map" be able to do all one needs? Or may there be cases where you would want to stay with the custom MKMapView but using UIViewRepresentable to bring it into SwiftUI
Topic:
UI Frameworks
SubTopic:
SwiftUI
Tags: