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

FROM : Keary Suska
DATE : Mon Nov 26 03:11:48 2007

on 11/24/07 7:38 PM, <email_removed> purportedly said:

> Well, for one, Apple's own "joystick" example overrides it:
>
> http://developer.apple.com/documentation/Cocoa/Conceptual/CocoaBindings/Concep
> ts/HowDoBindingsWork.html


I believe in this case they are being merely illustrative. You get bindings
support for free. You only need to override the method when you need
additional behavior, which is uncommon, IMHO. Hence, the question.

>> 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.


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