http://bugzilla.novell.com/show_bug.cgi?id=548346
http://bugzilla.novell.com/show_bug.cgi?id=548346#c7 Craig Dunn <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium CC| |craig.d...@conceptdevelopme | |nt.net Severity|Normal |Major --- Comment #7 from Craig Dunn <[email protected]> 2010-01-21 10:19:11 UTC --- I still see this error (on 1.4.5). Made some notes on the forum: http://forums.monotouch.net/yaf_postsm953.aspx#post953 My "guess" is (as I said in the forum) that it is related to whether the MKUserLocation annotation is on the MKMapView when you access the .Annotations property. Seems to break when the blue dot is there, but works when it's not. I've managed to make it "work" both by setting Map.ShowsUserLocation = false; but _also_ by calling the .Annotations property _quickly_ before CoreLocation has figured out where I am -- so .Annotations will work straight away, but fail once the blue dot has dropped in. Apple's doco says of MKMapView.Annotations "The objects in this array must adopt the MKAnnotation protocol" And of MKUserLocation "Conforms to: MKAnnotation, NSObject" However in MonoTouch... MKAnnotation : NSObject MKUserLocation : NSObject -- no common ancestor, therefore impossible to return in MKAnnotation[] I could be way off - all this is just based on observation. I have tested on simulator and device with Map.ShowsUserLocation = false AND = true... seems to confirm the observation (.Annotations property only works when no MKUserLocation is present). Much like MKMapView.AddAnnotationObject(NSObject) was added to the API, perhaps NSObject[] MKMapView.AnnotationObjects makes sense? HTH cd -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
