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: G S <email@hidden>
- Date: Fri, 02 Mar 2012 01:28:48 -0800
>
> How do you know the white view is screen-sized and has no superview?
> Actually a UIView which you can see and yet has no superview is probably
> just the UIWindow itself.
>
I write info about it to a log, in viewDidLoad.
How about the view which has just been loaded? Does it have a superview?
That is the white view.
Probably won't at that point, it's only been loaded, not moved into place.
> Go override the viewWillAppear:/viewDidAppear: methods and see if they get
> called.
>
I'll try that.
One question, there's no non-standard UIViewController usage here right? ie
> you have just ONE view controller for each screen
Yep. It's a very straightforward structure. Someone taps on a tableview
row, and we push the controller onto the navigation stack.
What's showing on the screen when this viewcontroller of yours is getting
> blown away by a memory warning, and how did that new content get there?
>
It's the photo-picker (actually a view that presents the photo picker and
then lets the user add a caption). It's presented with
presentModalViewController and dismissed by the delegate, as is typical.
The Apple photo picker often results in memory warnings (based on various
forum posts I've seen). It's after the dismissal of the picker's owning
controller that the white screen is revealed.
Thanks a lot for the follow-up.
Gavin
_______________________________________________
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