• 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: NSObject's bind:toObject:forKeyPath:options
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSObject's bind:toObject:forKeyPath:options


  • Subject: Re: NSObject's bind:toObject:forKeyPath:options
  • From: Mark Piccirelli <email@hidden>
  • Date: Fri, 30 Nov 2007 20:50:40 -0800

On Nov 24, 2007, at 12:26 AM, Mike R. Manzano wrote:

What does NSObject's implementation of bind:toObject:forKeyPath:options: do?

Should my class' implementation of it call it on its superclass?

It should if it doesn't recognize the passed-in binding name. See the comments in the override of it in Leopard /Developer/Examples/AppKit/ Sketch/SKTGraphicView.m.


David's summary of what the default implementation does was spot on. SKTGraphicView shows an example where that default implementation isn't good enough though. It has to override -unbind: too, to match.

-- Mark
_______________________________________________


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


References: 
 >NSObject's bind:toObject:forKeyPath:options (From: "Mike R. Manzano" <email@hidden>)

  • Prev by Date: Re: Why shouldn't I release?
  • Next by Date: Re: Creating subviews programmatically ?
  • Previous by thread: Re: NSObject's bind:toObject:forKeyPath:options
  • Next by thread: Re: NSObject's bind:toObject:forKeyPath:options
  • Index(es):
    • Date
    • Thread