iphone - NSManagedObject subclass conform to the <MKAnnotation> protocol? -


mainprofile = "text">

My main problem is accumulating the data that is not supported by core data. I already have a CLLocation property one variable Is stored as a specialty. I think the right approach is to declare a transient coordinate asset. Although I continue to receive errors with EXC_BAD_ACCESS

Edit:

My current subclass is the following interface:. 

  #import & lt; Foundation / Foundation.h & gt; #important & lt; Coralocace / Core Lection. H & gt; @Intefase Event: Nsmanyaged Object {} @ Property (Nonomatic, Written) NSSTING * Title; @property (nontomic, raten) NSDT * timestamp; @property (nonatomic, retain) CLLocation * location; @end

So I need to add 

  @property (nonatomic, readonly) CLLocationCoordinate2D coordination;

and 

  - (zero) setCoordinate: (CLLocationCoordinate2D) newCoordinate;

(SetCoordinate is optional, but I need this if I want to drag annotation)

In core data, the property of the property is variable And I use the @ dynamic in the implementation to generate accessors I am using the full code of this property, so I do not want to keep it.

I think the best way to go about it is to define the property of my coordinates in the transient form, but I Certainly not doing wrong with some implementation 

  - Coordinate {CLLocationCoordinate2D} {CLLocationCoordinate2D core = CLLocationCoordinate2DMake (self.location.coordinate.latitude, self.location.coordinate.longitude) ; Return core; } - (zero) setCoordinate: (CLLocationCoordinate2D) newCoordinate {CLLocation * newLoc = [[CLLocation alloc] initWithLatitude: newCoordinate.latitude longitude: newCoordinate.longitude]; [Self. Space release]; Self.location = newLoc; }

I have tried many ways, but this is the most recent one.

Edit 2: In EXC_BAD_ACCESS: 

  _kvcPropertysPrimitiveSetters

You can conform to an NSManagedObject subclass that you wish to do until the protocol somehow does not override the management of the context of the examples MK affirmation protocol should be completely secure. I

< P> Update:

Your problem is most likely here: 

  - (zero) setCoordinate: (CLLocationCoordinate2D) newCoordinate {CLLocation * newLoc = [[C LLocation alloc] initWithLatitude: newCoordinate.latitudeLength: newCoordinate.longitude]; [Self. Space release]; // & lt; - Do not release the properties! Self.location = newLoc; }

Generator accessories will retain for you when you leave them straight, then you screw that management you are also leaking newLoc . Try: 

  - (zero) setCoordinate: (CLLocationCoordinate2D) newCoordinate {CLLocation * newLoc = [[CLLocation alloc] initWithLatitude: newCoordinate.latitude longitude: newCoordinate.longitude]; Self.location = newLoc; [New release]; }