This may be obvious to people, but it took me a while to figure out, so I thought I'd post it in case it saves someone a bit of time.
My application is structured with a split view controller as the main interface element. The root view has a primary controller, and a second one which is pushed onto it by means of clicking a toolbar button on the detail view. When the primary controller is active, the button is enabled; when the second one is active, the button is disabled. All is good, except.... The application also presents a full screen modal view according to a user request, with a button to dismiss it. Very rarely, when the modal view is dismissed and the second controller is active, the button to select the second controller shows as enabled. There is no code path in the app that allows that. The answer is: if there is a memory warning delivered while the split view controller is obscured, its controllers dump their views and reload them when needed. Of course they reload them in whatever state they're defined in the nib file. Lesson: assuming that nib settings are only for application start up is wrong. _______________________________________________ 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
