Re: Problems subclassing NSTableView and NSOutlineView
Re: Problems subclassing NSTableView and NSOutlineView
- Subject: Re: Problems subclassing NSTableView and NSOutlineView
- From: Scott Anguish <email@hidden>
- Date: Thu, 7 Jul 2005 02:14:54 -0400
On Jul 7, 2005, at 1:14 AM, Todd Blanchard wrote:
Do I need to add ivars to hang onto the controller, value
transformer, etc as in the example code in the joystick view in
"How bindings work" or is this just meant to illustrate what is
going on? That seems like an awful lot of boilerplate for each
binding - why does the controller not manage all of this - or does it?
No, the controller doesn't manage it. NSBinder isn't public, so
you have to implement it yourself. You can do that as the example
does (put it all in the one place) or you could create a class that
encapsulates a binding, the value transformer, etc...).
that example is largely for illustrative purposes as you've
guessed.
If you're only subclassing to add a new binding, and you can
deal with being Tiger only, then you don't need cache values provided
in other bindings that you might need... you can use -infoForBinding:
to get the settings of a specific binding on the superclass.
Its also not clear how I get IB to provide UI for setting up the
bindings.
Am I supposed to write a pallet for my NSOutlineView subclass or what?
Yes. That's the only way to get IB to see it. IB will ask the
class for it's exposedBindings, but beyond that you're limited. You
can do it programmatically without building a palette.
I have submitted my feedback regarding the docs - they're awful.
thanks for the feedback
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden