FROM : Mike R. Manzano
DATE : Sun Nov 25 03:38:14 2007
Well, for one, Apple's own "joystick" example overrides it:
http://developer.apple.com/documentation/Cocoa/Conceptual/CocoaBindings/Concepts/HowDoBindingsWork.html
> on 11/24/07 1:26 AM, Keary Suska 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"
DATE : Sun Nov 25 03:38:14 2007
Well, for one, Apple's own "joystick" example overrides it:
http://developer.apple.com/documentation/Cocoa/Conceptual/CocoaBindings/Concepts/HowDoBindingsWork.html
> on 11/24/07 1:26 AM, Keary Suska 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"
| Related mails | Author | Date |
|---|---|---|
| Mike R. Manzano | Nov 24, 09:26 | |
| Keary Suska | Nov 24, 17:38 | |
| Mike R. Manzano | Nov 25, 03:38 | |
| David Spooner | Nov 25, 17:16 | |
| Keary Suska | Nov 26, 03:11 | |
| Mark Piccirelli | Dec 1, 05:50 |






Cocoa mail archive

