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
Post not yet marked as solved
quite related I was hoping to user Camera to do this but got stuck so created separate ticket - https://developer.apple.com/forums/thread/744107#744107021
Post not yet marked as solved
PS another way to ask this question might be - Within the view, how can I arrange for some code to be run each time a value within "newlocationManager" (which references the @Observable NewLocationManager instance) changes? (so within this code I can decided to update the Map position centering on this new location or not)
ok thanks - I tried move to using the MKMapCamera and not using userTrackingMode and this seems to work...
Post not yet marked as solved
get any updated/feedback?
Is this possible on iPhone/IOS?
Post not yet marked as solved
interested in solution for this too
Post not yet marked as solved
Any update on this item? Should NavigationLink's not be put into the Navigation bar? Or is there a bug in IOS here?
(by the way it worked per your code suggestion - no use of private contact)
thanks Jim - I'll try this - by the way do you create a private context to use performBlock? Or are you using this with the main context (a NSMainQueueConcurrencyType)? Just looking up performBlock (Xcode is telling me it's renamed to perform) and how to use and often they seem to use it with a private NSPrivateQueueConcurrencyType context you create(?)...
Post not yet marked as solved
Is it the case that that Xcode's ability to compile/function correctly does relate to your Mac hardware spec? I'm starting to assume yes. I'm getting the following error when I wouldn't have thought I should for example:"The compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions"So it's as if my MacBookPro is taking too long, and so this is what get's thrown up?I'm on: * MacBook Pro (15-inch, Mid 2012),* 2.6 GHz Quad-Core Intel Core i7( 8 GB 1600 MHz DDR3
Post not yet marked as solved
me too (I am using a simulator as opposed to real device - assume this is ok?)
