• 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
Delegates - I give up
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Delegates - I give up


  • Subject: Delegates - I give up
  • From: William Squires <email@hidden>
  • Date: Mon, 21 Jan 2008 04:53:05 -0600

Okay, I'm beginning to think the whole "delegate" system needs some help. Namely, they don't seem to be self-documenting. In REALbasic, if one wants to know what a "control" can do, examine its events in the code editor window. You can then put code there to handle that event.
But with delegates, how do you find out (easily) what delegates a control has, short of going to XCode help/documentation? And, more to the point, where to put the delegate methods?
Is there a better paradigm for thinking about controls/delegates? If so, please clue me in!
And, for that matter, what's the difference between a delegate and an action? (besides the fact that you can connect actions in IB)


_______________________________________________

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


  • Follow-Ups:
    • Re: Delegates - I give up
      • From: "I. Savant" <email@hidden>
    • Re: Delegates - I give up
      • From: Alastair Houghton <email@hidden>
  • Prev by Date: Re: why are there zero examples in the cocoa docs?!
  • Next by Date: Re: new API for MacBook Air for Multi-touch trackpad?
  • Previous by thread: Re: How many items can add into table view
  • Next by thread: Re: Delegates - I give up
  • Index(es):
    • Date
    • Thread