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

Target-Actions and Outlets


  • Subject: Target-Actions and Outlets
  • From: Steve Weller <email@hidden>
  • Date: Wed, 13 Jul 2005 22:12:29 -0700


I understand how Target-Actions are set up in code and in IB to make connections between methods that perform the actions in the controller and the interface elements that the user interacts with.


I also understand how Outlets are set up in code and IB and are used to provide a reference held in an instance variable that points to an user interface element that the code is to manipulate.

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?


--

How much art could an artichoke choke if an artichoke could choke art?
_______________________________________________
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


  • Follow-Ups:
    • Watch me learn Cocoa
      • From: Steve Weller <email@hidden>
    • Re: Target-Actions and Outlets
      • From: mmalcolm crawford <email@hidden>
  • Prev by Date: More binding questions
  • Next by Date: Re: Target-Actions and Outlets
  • Previous by thread: Re: Multiple pasteboard items
  • Next by thread: Re: Target-Actions and Outlets
  • Index(es):
    • Date
    • Thread