• 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: Keary Suska <email@hidden>
  • Date: Sat, 24 Nov 2007 09:38:58 -0700
  • Thread-topic: NSObject's bind:toObject:forKeyPath:options

on 11/24/07 1:26 AM, email@hidden purportedly said:

> What does NSObject's implementation of
> bind:toObject:forKeyPath:options: do?
>
> Should my class' implementation of it call it on its superclass?

I would ask, why do you feel the need to override the method? Binding
structures have introspection, if you needed that. Otherwise, I would say,
yes, if you override it, you should call the method on super.

Best,

Keary Suska
Esoteritech, Inc.
"Demystifying technology for your home or business"


_______________________________________________

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: Adding playlists to iTunes with SB
  • Next by Date: Capturing NSLog in Leopard
  • Previous by thread: NSObject's bind:toObject:forKeyPath:options
  • Next by thread: Re: NSObject's bind:toObject:forKeyPath:options
  • Index(es):
    • Date
    • Thread