On Mar 19, 2014, at 10:11 AM, Quincey Morris <quinceymor...@rivergatesoftware.com> wrote: > >> On Mar 19, 2014, at 09:52 , Kyle Sluder <k...@ksluder.com> wrote: >> >> This doesn’t sound like a good idea to me. There is no guarantee that >> opening an NSDocument will cause it to create an interface—see AppleScript, >> printing from the Finder’s contextual menu, etc. > > Perhaps so, but it seems to me that there’s even less justification for > re-saving the file in these scenarios than there was in the original scenario.
That’s probably a true statement, but it’s orthogonal. You should not rely on the side effect of a “nib loaded” notification to do something as fundamental as dictate your document’s data lifecycle. Remember that it is also perfectly valid to implement -makeWindowControllers in a way that doesn’t ever touch a nib. --Kyle Sluder _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
