On Apr 3, 2010, at 12:05, Ben Trumbull wrote: > The canonical solution is to tell your controller objects like > NSArrayController to refetch from the new document. It sounds like you're > fighting the document based Save As behavior. It's "close the existing > document, save the current state to a new document, open new document"
Do you mean "fighting the NSPersistentDocument Save As behavior"? My understanding is that "close the existing document, save the current state to a new document, open new document" is *not* the semantics of plain NSDocument Save As -- the whole point being that transient state is preserved across a Save As. No NSDocument-based (non-NSPersistentDocument-based) application is required to discard all of its in-memory object references after doing a Save As, as far as I'm aware. _______________________________________________ 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
