Re: What are the conditions for NSManagedObjectContextObjectsDidChangeNotification to get posted?
Re: What are the conditions for NSManagedObjectContextObjectsDidChangeNotification to get posted?
- Subject: Re: What are the conditions for NSManagedObjectContextObjectsDidChangeNotification to get posted?
- From: Mike Abdullah <email@hidden>
- Date: Thu, 16 Jan 2014 16:02:03 +0000
On 15 Jan 2014, at 21:04, Jerry Krinock <email@hidden> wrote:
> Hello Jim,
>
> The fact that no one has replied to your post yet confirms my feeling that you’re at the bleeding edge of NSManagedObjectContextObjectsDidChangeNotification usage. Here are a couple of thoughts…
>
> • You can generally send -processPendingChanges yourself, whenever you want. Particularly in a text editing context, there is no (performance) reason not to. Or you could place a log-and-continue breakpoint on it.
>
> • Cocoa Bindings are just as mysterious as NSManagedObjectContextObjectsDidChangeNotification, maybe more so. Might be good to verify that your model object is actually being changed with each keystroke.
I think your first debugging port of call is try and figure out a few things:
- Does NSManagedObjectContextObjectsDidChangeNotification ever get posted *not* as a result of -processPendingChanges?
- When you start seeing the problematic behaviour, is -processPendingChanges still being called, but not firing off the notification? Or is it also not being called itself?
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden