Re: programmatically adding model objects to NSOultineView/NSTreeController
Re: programmatically adding model objects to NSOultineView/NSTreeController
- Subject: Re: programmatically adding model objects to NSOultineView/NSTreeController
- From: Ken Victor <email@hidden>
- Date: Tue, 12 Jun 2007 09:38:33 -0700
At 10:08 PM -0700 6/10/07, mmalc Crawford wrote:
On Jun 10, 2007, at 11:09 AM, Ken Victor wrote:
thanx for the pointer. i can't tell you how many times i've read
this! :-) and i just reread to make sure i wasn't missing
anything. note: nowhere does this say whether or not NSProxy
implements any of the KVO/KVC protocols
KVOutlineObjectProxy != NSProxy.
sorry for the confusion/lack of accuracy... KVOutlineObjectProxy
is a subclass of NSProxy.
I think it's reasonable to expect that the documentation would state
if NSProxy did adopt other protocols.
It's not clear why you're inheriting from NSProxy,
well... it seemed like the right thing to do at the time! :-)
actually, i wanted a proxy object that could stand-in for a number of
different objects and NSProxy seemed like just the right thing. and
it worked in many situations. in fact, it didn't really fall down
until i started making more use of bindings.
but fundamentally -- since NSProxy doesn't adopt the necessary
protocols -- it's not going to work with bindings etc.
i've started my conversion to use a subclass of NSObject (instead of
subclassing NSProxy). and although this will take a little while, in
terms of coding and testing, at first glance it does appear to be
solving my bindings related problem (of new first child not showing
up in outline views bound to a tree controller).
thanx,
ken
mmalc
_______________________________________________
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
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden