Re: didReceiveMemoryWarning doesn't release view...
Re: didReceiveMemoryWarning doesn't release view...
- Subject: Re: didReceiveMemoryWarning doesn't release view...
- From: Robert Marini <email@hidden>
- Date: Mon, 12 Jan 2009 14:51:15 -0500
Are you ever releasing the view? Similarly, have you overridden
didReceiveMemoryWarning in your view controllers?
-rob.
On Jan 12, 2009, at 1:26 PM, Oscar Alejandro Alvarado Prieto wrote:
Hi there.
I'm using a table view controller inside a navigation controller
wich is a
view controller of a tab bar controller. As I want take care of memory
warnings, I put the table view in a separated nib file, setting the
file's
owner class to my table view controller subclass and all other
thinks (view
outlet, nib file name, etc). It seems to work fine but when a memory
warning
is generated using simulator, the table view is not released.
I set breakPoints on setView and loadView and they are called only
first
time view is needed.
I read that the view is released if it "doesn't have a superview"
but I
discovered my view has a UITransitionView superview ¿...?.
Please, is there someone who know what could be going on?.
I'm stuck with this silly thing.
Tx in advance.
--
Oscar A. Alvarado
_______________________________________________
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
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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