Re: Dependent Keys
Re: Dependent Keys
- Subject: Re: Dependent Keys
- From: Jim Hamilton <email@hidden>
- Date: Fri, 19 Aug 2005 15:10:18 -0400
Hi Bill. I've been away for a couple of days, and just saw this:
On Aug 17, 2005, at 5:55 PM, Bill Cheeseman wrote:
NSManagedObjectContextObjectsDidChangeNotification's userInfo
dictionary contains three sets of objects. An object that depends on
attributes of other objects can iterate them, looking for the objects
whose changes should propagate through.
I'm discovering that there can be timing issues with this
notification. I
think this is the right approach, but for some reason I find that this
notification doesn't get issued in time to update the user
interface in some
situations.
Would you care to elaborate? What, exactly, do you mean by "this
notification doesn't get issued in time"?
FWIW, when I needed to do this, it was for exactly one relationship
in my model. The change is always triggered by the user making some
selection/connection, and the change propagates to one cell in an
NSTableView. I don't notice any delay in the UI; perhaps that's
because I'm not trying to do too much with one event... and, I could
easily tolerate it, in any case.
[Another FWIW: the OP took some code I sent him in a private
message, and reported that it solved his problem exactly. It sounded
like his issue was similar to mine.]
I suppose, if time is that important, the triggering object could
send a message directly to the dependent object; of course, that
requires a subclass of NSManagedObject for (at least) the triggering
entity. Any thoughts?
Thanks,
Jim H
--
Jim Hamilton
email@hidden
email@hidden
_______________________________________________
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