• 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: Target-Actions and Outlets
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Target-Actions and Outlets


  • Subject: Re: Target-Actions and Outlets
  • From: mmalcolm crawford <email@hidden>
  • Date: Wed, 13 Jul 2005 22:29:15 -0700


On Jul 13, 2005, at 10:12 PM, Steve Weller wrote:

When is it appropriate to use outlets et al and when to use bindings? I see some example code doing things one way, some mixing the two, and some taking glee in eradicating the IBOutlets from the code. I am trying to understand the reasons for using one over the other.
Bindings appear to do more for me. Do they have a downside that only outlets can fill?


There isn't a "right" answer. Use whichever is more convenient in the circumstances. If you want a simple action method to be invoked when a button is pressed, there's no need to use bindings -- target/ action works fine. If the action method serves as a "cover" for a method that retrieves the selection from a table view, the state from a switch, and passes them on to another controller, then this might be a candidate for setting up a target/action binding.

mmalc

_______________________________________________
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: 
 >Target-Actions and Outlets (From: Steve Weller <email@hidden>)

  • Prev by Date: Target-Actions and Outlets
  • Next by Date: Re: More binding questions
  • Previous by thread: Target-Actions and Outlets
  • Next by thread: Watch me learn Cocoa
  • Index(es):
    • Date
    • Thread