• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Dealing with NSError outside of the Responder chain
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Dealing with NSError outside of the Responder chain


  • Subject: Re: Dealing with NSError outside of the Responder chain
  • From: Paul Sargent <email@hidden>
  • Date: Tue, 27 May 2008 23:15:42 +0100


On 27 May 2008, at 21:24, Adam R. Maxwell wrote:

In general, I think you're supposed to add NSError** parameters to pass it back up to some class that knows how to present an error, but I find that's not always practical, and it tends to be messy. In such cases I typically take the easy way out and call [NSApp presentError:].

Makes sense. Hadn't noticed NSApp had a presentError method. Thanks _______________________________________________

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: 
 >Dealing with NSError outside of the Responder chain (From: Paul Sargent <email@hidden>)
 >Re: Dealing with NSError outside of the Responder chain (From: "Adam R. Maxwell" <email@hidden>)

  • Prev by Date: [moderator] Re: if statement
  • Next by Date: Re: Date compiled?
  • Previous by thread: Re: Dealing with NSError outside of the Responder chain
  • Next by thread: Okay I have those pieces… now where's the glue?
  • Index(es):
    • Date
    • Thread