Thanks for the help guys. That makes a lot of sense now.

On 14 Apr 2011, at 01:53, Matt Neuburg wrote:

> On Wed, 13 Apr 2011 16:42:40 -0700, Chris Parker <[email protected]> said:
>>> 2011-04-14 00:03:09.640 CRDev[18309:307] InGameViewController 
>>> implementation of -viewDidUnload caused the view to be reloaded. This will 
>>> adversely impact system performance.
>> 
>> The log is trying to help you out; -viewDidUnload is called when the view 
>> controller has discarded its view. The log is telling you that an 
>> implementation of -viewDidUnload is causing the view to be loaded again.
>> 
>> This can be caused by doing anything which accesses the -view property on 
>> the view controller inside the -viewDidUnload implementation.
> 
> That's really kind of wonderful.
> 
> In my iOS book I talk about discovering that my loadView was being 
> mysteriously called twice, and then (by logging like crazy) realizing that 
> this due to my mentioning the view property in my awakeFromNib. That's how I 
> learned not to do that. :) I really applaud verbose explanatory log messages 
> from the framework such as this. m.
> 
> --
> matt neuburg, phd = [email protected], <http://www.apeth.net/matt/>
> A fool + a tool + an autorelease pool = cool!
> Programming iOS 4!
> http://www.apeth.net/matt/default.html#iosbook_______________________________________________
> 
> Cocoa-dev mailing list ([email protected])
> 
> 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:
> http://lists.apple.com/mailman/options/cocoa-dev/mslinklater%40gmail.com
> 
> This email sent to [email protected]

_______________________________________________

Cocoa-dev mailing list ([email protected])

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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to