Woah.
If you really want to use a custom cell, you're gonna want a custom
column as well. The bindings for the tableColumn come from the
tableColumn's dataCell's available bindings. Yea, as you've found,
NSActionCell has a value binding, not plain old NSCell.
[.. snip ..]
Does any of this make sense?
Possibly, you've already solved this some other way, but hopefully
I've cleared up a couple of things.
Yeah, this all mostly makes sense. I'm content just subclassing
NSActionCell for this case, though.
FWIW, what I am trying to do is create a circular, nondeterminate (pie
chart style) progress indicator cell and use it in a table column. So
it's just doing some drawing based on objectValue (I'm using nil to
mean hide the progress). Of course, I want to use bindings to hook
this up to my model, too. Subclassing NSCell and binding the column's
"value" seemed like the best approach.
-Dave
_______________________________________________
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
