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: Wed, 29 Feb 2012 10:23:23 -0800
> Date: Tue, 28 Feb 2012 22:36:38 -0800
> From: G S <email@hidden>
> To: cocoa-dev <email@hidden>
>
>
> So I did override loadView, simply to write to a log and then call [super
> loadView].
If you override loadView you must *not* call super. To put it another way, don't implement loadView unless you mean it (i.e. you intend that your view will be set here, or a generic view should be supplied here). To put it another way, he who lives by messing with the framework dies by messing with the framework; part of the way the framework decides what you want is by looking to see what methods you've implemented, so you can't play fast and loose like this. m.
--
matt neuburg, phd = email@hidden, http://www.apeth.net/matt/
pantes anthropoi tou eidenai oregontai phusei
Programming iOS 5! http://shop.oreilly.com/product/0636920023562.do
RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
TidBITS, Mac news and reviews since 1990, http://www.tidbits.com
_______________________________________________
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