• 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: NSAlert strategy advice
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSAlert strategy advice


  • Subject: Re: NSAlert strategy advice
  • From: Larry Fransson <email@hidden>
  • Date: Fri, 17 Dec 2004 23:07:41 -0800


On Dec 17, 2004, at 19:06, Henry Maddocks wrote:

I know it was sort of a dumb question, but having a bunch of similar named functions that almost do the same thing is a recipe for a cockup. I was hoping someone had come up with some clever pattern to reduce the maintenance. Maybe using contextInfo and some funky selector thing or maybe wrapping them up in their own object...

I have used the contextInfo to determine what action to take when I have multiple alerts calling a single function.


Larry Fransson
Seattle, WA

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >RE: NSAlert strategy advice (From: "John Stiles" <email@hidden>)
 >Re: NSAlert strategy advice (From: Henry Maddocks <email@hidden>)

  • Prev by Date: Re: Wrapping an Interactive Unix Executable (update)
  • Next by Date: Using NSSearchField's setRecentSearches: method.
  • Previous by thread: Re: NSAlert strategy advice
  • Next by thread: Re: NSAlert strategy advice
  • Index(es):
    • Date
    • Thread