On Aug 1, 2009, at 12:38, Jerry Krinock wrote:
On 2009 Aug 01, at 05:11, Squ Aire wrote:
2) Which brings me to the second option. Keep the undo stuff there
so that the NSManagedObjectContextObjectsDidChangeNotification will
properly be sent out, as I want. However, instead just get rid of
the Undo and Redo menu items.
I'd say it's quite reliable!
If that's going to be the solution, I'd suggest also doing
'document.undoManager.levelsOfUndo = 1'. (In OldSpeak: '[[document
undoManager] setLevelsOfUndo: 1]'.)
WRT the larger issue, we know that there's nothing accidental in the
Core Data APIs. It's *possible* that this is a defect in the Core Data
design (needing undo enabled in order to get change notifications),
but it's also *possible* that there's a carefully thought-out reason
why the two things are linked. (For example, that the information
needed to produce the notifications is precisely the same as the
information needed for undo. So, beyond removing the menu items and
limiting the number of undo actions as above, the perceived need to
turn off Core Data undo may be imaginary.)
Did you post here in general about the limitations you found in using
the notifications? It's likely you posted specifics, but was there a
higher level discussion that I don't recall?
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
