Re: CORE DATA: setImage (transient) and setImageData (binary) accessors don't fire.
Re: CORE DATA: setImage (transient) and setImageData (binary) accessors don't fire.
- Subject: Re: CORE DATA: setImage (transient) and setImageData (binary) accessors don't fire.
- From: "Frederick C. Lee" <email@hidden>
- Date: Sun, 15 Jan 2006 09:49:18 -0800
On Jan 15, 2006, at 12:45 AM, Frederick C. Lee wrote:
> Specifically, the 'setImageData' accessor isn't firing.
>
> I don't know why.
One possibility is that in your data model, you haven't specified the
entity's class but rather left it at the default value of
NSManagedObject. If you don't specify this, it will go right to
valueForKey: and setValue:forKey: and not use your accessors
I checked the code and re-affirmed that the Map entity is correctly
defined by the 'MapManagedObject'
subclass. The other entities are 'NSManagedObjects'.
The 'MapManagedObject' has the added 'setImage' and 'setImageData'
accessors.
Just for the sake of confirmation of my problem, I changed
'imageData' datatype from binary to string,
disconnected the NSImageView and placed a NSTextField in the GUI and
bind it to 'imageData'.
Sure enough, 'setImageData' fired.
When I return to the original configuration, 'setImageData' did NOT
Fire.
Then I changed the binding of the NSImageView from 'view' to
'data'. And bind it directly to
'imageData' binary (vs 'image' transient). Again, 'setImage' and
'setImageData' did NOT fire.
So there's something about being a non-string here, that doesn't
allow the SET accessor to fire.
That's the problem.
And so far, I can't figure it out.
So the question is, how does NSManagedObject effect binary accessors
differently from strings??
Any clues, suggestions....remedies?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden