On 2009 Mar 11, at 18:39, Dave Fernandes wrote:
It helped me figure out what was changing by overriding
willChangeValueForKey in my NSManagedObject subclass...
Dave, I just used your idea and was able to track down two of these
phantom changes this afternoon.
At first, I was getting info
I recently had this problem when opening existing documents in Tiger.
No problem in Leopard. It helped me figure out what was changing by
overriding willChangeValueForKey in my NSManagedObject subclass. (You
are never supposed to do this in shipping code.)
#ifdef DEBUG_MANAGED_OBJECT_CHANGE
On Jan 23, 2009, at 22:44, Jerry Krinock wrote:
I realize I could probably paper over this problem by disabling undo
registration during the import
The stack trace clearly shows that an undo action is being recorded,
which means that some property has been changed. ("Changed" in the
sense
In my Core Data Document-Based application, I have a menu item which
imports settings from a legacy application. For each setting found,
it programatically creates a new document, saves it, and leaves the
new document window open. When all done, the user gets a modal dialog
showing a list
