On Tue, Feb 8, 2011 at 9:29 PM, Graham Cox <graham....@bigpond.com> wrote: > I'm trying to prevent NSDocument from doing any saving at all, for a demo > version of my app. I need to suppress the menu commands (done) and all the > automated UI such as the 'save changes' dialog and 'Save As' dialog even > though the doc is marked dirty. I've also removed the actual save code. > > According to the docs for > -canCloseDocumentWithDelegate:shouldCloseSelector:contextInfo:, if I > immediately pass YES to the should close selector, it should accomplish this. > Indeed, it does suppress the "do you want to save changes?" dialog, but the > window does not close. > > What's the proper way to do this? I searched the archives but surprisingly I > couldn't find any previous discussion of this, even though I would have > thought it's quite a common thing.
If you've removed the actual save code, why not simply let Cocoa go through the motions and call your (empty) save method? Seems like a lot of unnecessary trouble to go through, just to make it avoid calling a method that isn't going to do anything anyway... sherm-- -- Cocoa programming in Perl: http://camelbones.sourceforge.net _______________________________________________ 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
