On Aug 3, 2009, at 13:24, Chase Meadors wrote:
Maybe I'm missing what you mean here, but if I do that, then what
should I do in the objectValueFor... method?
On Aug 3, 2009, at 2:13 PM, Quincey Morris wrote:
Yes, but according to that message you *didn't* set the correct
selection index in #1. I really think that's what you need to do.
The objectValue... method should return the index of the selected menu
item, because that's what the value is for that column.
I'm going to change my earlier answer on the other part.
When you don't implement tableView:datCellForTableColumn:row:, the
table view obviously has to set the object value of the (shared) cell
it knows about for each row, and it would do that by calling the
objectValue... data source method *after* it has found the cell to
use. My *expectation* would be that it'd do the same thing for the
result of dataCell..., but the documentation doesn't say anything
about that one way or the other.
So I would still try having dataCell... retrieve the selected menu
item index (possibly by calling objectValue... directly) and see if
setting it solves the problem. If so, then answer is apparently that
dataCell... is required to set up the desired object value. If not,
this is a false trail.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please 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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
