• 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: Cocoa bindings and reluctance to use NSPopupButon
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cocoa bindings and reluctance to use NSPopupButon


  • Subject: Re: Cocoa bindings and reluctance to use NSPopupButon
  • From: "Stuart Rogers" <email@hidden>
  • Date: Mon, 19 May 2008 13:51:07 +0100

David <email@hidden> wrote:

So, I'm realizing that maybe its more reasonable to back down to just using a data source, target/action and delegates.

Don't think of it as backing down; think of it as using a more appropriate
technology. (For some appropriate definition of 'appropriate' of course.)


I'm still having trouble understanding the delegate signatures when
they throw in some (id) types, I'm not sure what data types are
expected.

You don't need to know. All that's needed is that the delegate implement
certain methods. See the reference docs for the class that uses the
delegate for the expected methods - they're usually listed at the end
of the class's list of tasks, and are usually flagged as required or
optional.


Stuart

_______________________________________________

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


  • Prev by Date: Re: Cocoa et al as HCI usability problem
  • Next by Date: Re: [OT] generating API docs
  • Previous by thread: Re: Cocoa bindings and reluctance to use NSPopupButon
  • Next by thread: Cocoa bindings and reluctance to use NSPopupButon
  • Index(es):
    • Date
    • Thread