> Date: Tue, 28 Feb 2012 22:36:38 -0800 > From: G S <stokest...@gmail.com> > To: cocoa-dev <Cocoa-dev@lists.apple.com> > > > 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 = m...@tidbits.com, 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 (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
