Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: debugging hard-to-locate error in NSApplication delegate

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: debugging hard-to-locate error in NSApplication delegate

Subject: Re: debugging hard-to-locate error in NSApplication delegate
From: Quincey Morris <email@hidden>
Date: Mon, 12 Jan 2009 17:47:40 -0800

On Jan 12, 2009, at 16:40, Keary Suska wrote:

I don't think this is precisely true, particularly for regular objects (the plain blue cube). At least, none of mine behave this way. Of course, none of the objects I use in this way implement NSCoding, and maybe that matters. All other non-view objects do instantiate with initWithCoder:, as I understand, just not generic custom objects.


Thanks for the correction (and to all who corrected me).

Can I ask for half credit for suggesting a reason that might have half explained the OP's problem if it had been a half valid reason? Well, never mind.


_______________________________________________

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



References:  
  >debugging hard-to-locate error in NSApplication delegate (From: Greg Beaver <email@hidden>)
  >Re: debugging hard-to-locate error in NSApplication delegate (From: Quincey Morris <email@hidden>)
  >Re: debugging hard-to-locate error in NSApplication delegate (From: Keary Suska <email@hidden>)




Prev by Date:
Re: debugging hard-to-locate error in NSApplication delegate

Next by Date:
Re: CALayer removeFromSupeLayer crashes

Previous by thread:
Re: debugging hard-to-locate error in NSApplication delegate

Next by thread:
Re: debugging hard-to-locate error in NSApplication delegate

Index(es):

Date
Thread