Sorry, I.S. I didn't mean to be rude or dismissive.
No problem.
-[NSNull identifier]: selector not recognized
For the record, I believe that this error is a clue that one of the
components of a long.key.path in a binding is not KVC.
I'm not entirely sure I'm right, but I'm going to say "not
necessarily".
I did isolate it to a particular component but after trying for some
time was unable to fix it. So I decided it would be easier to
simply not use bindings this time.
There are *many* cases where this ... well ... is the case. :-)
It's not perfect and it's not a catch-all, but Bindings is incredibly
flexible. In this case my nit was that the window controller /
document path absolutely works for me, but I wasn't sure whether your
own situation was really so special that it wouldn't. Of course it's
entirely possible (and somewhat probable) that it was ...
I use bindings for all simple cases, some more difficult cases, and
pretty much no complex cases. Not gospel, but just my own experience.
--
I.S.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
