> > No. But if you've presented a modal view controller, your entire view > hierarchy (self.view) has been ripped out of the window, and if a memory > warning arrives, then self.view will be set to nil. What happens next > depends on if you implemented -viewDidUnload properly or if your view > references are strong or weak. > > If they are strong and you did not implement -viewDidUnload properly, then > your view reference will be non-nil.
Not according to the Apple doc. By the time viewDidUnload is called, the view reference has already been set to nil: "viewDidUnload Called when the controller’s view is released from memory. - (void)viewDidUnload Discussion When a low-memory condition occurs and the current view controller’s views are not needed, the system may opt to remove those views from memory. This method is called after the view controller’s view has been released and is your chance to perform any final cleanup. If your view controller stores separate references to the view or its subviews, you should use this method to release those references. You can also use this method to remove references to any objects that you created to support the view but that are no longer needed now that the view is gone. You should not use this method to release user data or any other information that cannot be easily recreated. At the time this method is called, the view property is nil. " _______________________________________________ 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
