FROM : Mark Piccirelli
DATE : Sat Dec 01 05:50:40 2007
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
DATE : Sat Dec 01 05:50:40 2007
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
| 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

