On Fri, Mar 16, 2012 at 9:45 PM, Roland King <[email protected]> wrote: > I think chances are you are still somehow calling a method on a view > controller or similar which has been evicted. >
I took a hard look at the two underlying controllers to make sure that they are not referring to controls when the views aren't loaded. And that's another puzzle piece: It doesn't matter which of them I leave on the screen after I dismiss the modal view; it's gonna be white. If I have the controller that presented the modal view dismiss itself after dismissing the modal view, the one under that is white. If not, the one that presented and dismissed the modal view is white. These controllers also withstand many, many memory warnings and view reloads in normal operation without incident. By the way: I keep track of the view loaded/unloaded state with a flag in the view controller (which I toggle in viewDidLoad & viewDidUnload). Is this a typical strategy? This ensures that the controller's routines don't try to interact with the controls when they're unloaded. _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
