Re: How are views supposed to reload after being nillified by memory warnings?
Re: How are views supposed to reload after being nillified by memory warnings?
- Subject: Re: How are views supposed to reload after being nillified by memory warnings?
- From: Matt Neuburg <email@hidden>
- Date: Sat, 03 Mar 2012 08:57:25 -0800
On Fri, 02 Mar 2012 10:17:43 -0800, David Duncan <email@hidden> said:
>On Mar 2, 2012, at 1:28 AM, G S wrote:
>
>In the vast majority of cases where I've seen this behavior, it is because in your delegate handler for the UIImagePickerController, you assign the returned image directly to a UIImageView that you have in your view hierarchy. If you've recently gotten a memory warning, then this image view is either nil, or will be released very soon, and you will end up with a view that has no image.
So let's say I have a view controller. And let's say that its view (self.view) contains a UIImageView in its hierarchy (self.view.imageview). You are saying that the runtime might summarily rip the UIImageView out of the interface, so that self.view is *not* nil but self.view.imageview *is* nil???
m.
--
matt neuburg, phd = email@hidden, <http://www.apeth.net/matt/>
A fool + a tool + an autorelease pool = cool!
Programming iOS 5! http://shop.oreilly.com/product/0636920023562.do
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden