Know when a controller's view is released in didReceiveMemoryWarning

[obrand]

As a controller's view is only released in the didReceiveMemoryWarning method when such view is not currently displayed. Is it correct to perform this test in the didReceiveMemoryWarning method:

// Test if the view is attached to a superView
if([[self view] superView] == nil)
{
    NSLog(@"View is going to be released as not showing");
}

Is that piece of code Ok to test in the didReceivememoryWarning method the condition when the view is going to be released?

Thanks

B-

[PhoneyDeveloper]

It's not a great idea to do this. [self view] will always load the nib, call viewDidLoad etc. Even if the view was unloaded during the last memory warning it will now be loaded again.

If you do use this code anyway make sure it goes before calling super. You want to give the base class the opportunity to unload the view.

[obrand]

Thanks. I am not using Interface Builder in my application. Would the [self view] then forces the reload of the view in the didReceiveMemoryWarning method?

Originally Posted by PhoneyDeveloper

It's not a great idea to do this. [self view] will always load the nib, call viewDidLoad etc. Even if the view was unloaded during the last memory warning it will now be loaded again.

If you do use this code anyway make sure it goes before calling super. You want to give the base class the opportunity to unload the view.

[PhoneyDeveloper]

In that case it will call loadView and then viewDidLoad. I assume that you're building your self.view in loadView and/or viewDidLoad. So yes, it will cause the view to be reloaded even if you're not using IB.

You can easily test this in the Sim by using the Simulate Memory Warning menu item.

[obrand]

Great. Found out that the best way to handle this is to override the setView and check when the controller is passing nil to it.
When it does such thing, you can be sure that the view has been discarded.

B-