We're going to need a stack trace or *something* to offer anything helpful.
On 6 Feb 2010, at 04:59, Charles Burnstagger wrote: > The viewDidUnload: method for one of my iPhone app's views gets called even > when that view and all its subviews are still onscreen. (I assume in response > to the didReceiveMemoryWarning: message). > > Since the view and all of its subviews are still needed at that point (they > are onscreen), how should I respond to this? > > On the one hand, I want all my release code to run in viewDidUnload: when the > view does actually unload, but on the other hand, I don't want the view > unloading while it is still onscreen. > > What is the correct way to handle such situations? > > Thanks, > > Chuck > > > > > _______________________________________________ > > 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/cocoadev%40mikeabdullah.net > > This email sent to cocoa...@mikeabdullah.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
