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: Sun, 04 Mar 2012 18:50:36 -0800
Thanks for the feedback, Roland.
On Sun, Mar 4, 2012 at 6:07 PM, Roland King <email@hidden> wrote:
> I would suspect that and change it so that either
>
> 1 the new view controller is pushed by the viewDidDisappear of the
> dismissed modal one or
>
This would require excessive knowledge of the delegate controller on the
part of the modal controller.
2 knowing the view is just about to be rebuilt, override the memory warning
> handling not to dump the views, at least to that first level.
>
That was an early consideration, but I've seen forum posts from people who
did this and found it was not reliable (sometimes the views were dumped
anyway). Plus, I don't mind letting the memory-conservation mechanism
work; my controllers should be able to handle the reload. It's just that
the pertinent controller's view is never shown.
My next step will probably be to get rid of the creation of the detail
controller temporarily, to see whether the underlying root controller
recovers from the memory warning properly. If it does, I guess the
workaround will be to wait for the dismissed modal controller to disappear
before pushing the detail controller. Too bad, though, because that's
going to look janky.
_______________________________________________
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