Well, after after getting my first window to work using bindings in
Tiger, I get the following error when the window loads in Panther:
[<NSTableColumn 0xXXXXXXXX> valueForUndefinedKey:]: this class is not
key value coding compliant for the key enabled.
Yes, I have bound the "enabled" attribute of some NSTableColumns of
NSButtonCells (checkboxes, etc.).
So, I surmise from this error that such a binding was not supported
in Panther. But I looked in the API documentation of NSTableColumn,
its superclass and protocols, and find that the 'enabled' attribute
is not documented. So, I further surmise that NSTableColumn
'enabled' is one of those magical "bindings-only" attributes invoking
some Apple-private API.
But I'm not sure because I searched the release notes,
(Although I suppose that 'enabled' is an attribute, not an ^option^.)
I'd appreciate any answers to:
1. Am I correct, that the 'enabled' NSTableColumn attribute is not
supported in Panther bindings?
2. Is there a simple workaround? It seems I'd have to manually
implement KVO and send messages to the NSButtonCells; seems like a
real mess. I wouldn't mind just leaving the stupid checkboxes
enabled all the time for my few Panther users, but I suppose there is
no equivalent to "-respondsToSelector" in bindings?
3. If answer 1 is YES, is there any documentation or unofficial list
of other little surprises that are not supported in Panther
bindings? I sure hope I don't have to "guess, try, fix, retest,
repeat,..., release, respond to bug reports."
Thanks,
Jerry Krinock
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
