My point is not that I don't know how to fix it or cannot (as an absolute) fix it, but that it is not practical to fix it at this time, so I need a way to determine how the window was closed.
If you have never faced one of these situations before, just wait awhile...you will. On Mar 5, 2010, at 12:33 PM, Greg Guerin wrote: > Eric Gorr wrote: > >> The use of a global was considered and rejected. But, would likely be >> reconsidered if -windowShouldClose: does not work as expected. > > > Then add a category method that means "close but preserve open state for next > launch", and call that from the termination delegate. > > Or a category method that tells the receiver to copy its current open state, > which will then be written to disk when the next close message is received. > > I don't see a big difference in how the two things (user-close vs. > close-but-preserve-opened-state) are distinguished by the panels. Use > whatever makes sense for the code base. The key point is that the latter > only occurs at app termination. Tying it into app termination is what makes > it different. > > -- GG > > > _______________________________________________ > > 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/mailist%40ericgorr.net > > This email sent to mail...@ericgorr.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
