FROM : mmalcolm crawford
DATE : Tue Nov 30 09:03:20 2004
On Nov 29, 2004, at 11:24 PM, Brad Miller wrote:
> Binding the view back to my model. I'm manually binding [the custom
> subclass of NSTextView] with: [myTextView bind:@"value"
> toObject:documentController withKeyPath:@"selection.textValue"
> options:nil], which is the same binding I was using before. Launching
> the app give a class not KVC compliant message in the run log. From
> reading the docs and the list archives, I was under the impression
> that you can still bind to a values that a super class exposes.
>
There shouldn't be a problem with that. Are you overriding the
bind:... method? What is the actual error message (in particular, what
class are you being told is not KVC compliant)? It sounds like the
problem is with the bound-to object, not the view...
mmalc
DATE : Tue Nov 30 09:03:20 2004
On Nov 29, 2004, at 11:24 PM, Brad Miller wrote:
> Binding the view back to my model. I'm manually binding [the custom
> subclass of NSTextView] with: [myTextView bind:@"value"
> toObject:documentController withKeyPath:@"selection.textValue"
> options:nil], which is the same binding I was using before. Launching
> the app give a class not KVC compliant message in the run log. From
> reading the docs and the list archives, I was under the impression
> that you can still bind to a values that a super class exposes.
>
There shouldn't be a problem with that. Are you overriding the
bind:... method? What is the actual error message (in particular, what
class are you being told is not KVC compliant)? It sounds like the
problem is with the bound-to object, not the view...
mmalc
| Related mails | Author | Date |
|---|---|---|
| Brad Miller | Nov 30, 08:24 | |
| mmalcolm crawford | Nov 30, 09:03 | |
| mmalcolm crawford | Dec 1, 04:14 |






Cocoa mail archive

