Re: NSTableView + setObjectValue + NSCell
Re: NSTableView + setObjectValue + NSCell
- Subject: Re: NSTableView + setObjectValue + NSCell
- From: Corbin Dunn <email@hidden>
- Date: Tue, 28 Mar 2006 15:05:14 -0800
Hi JFB,
I'd suggest setting a breakpoint on -[NSException raise] and debugging
from there. This will tell you what is calling what where.
--corbin
On Mar 25, 2006, at 3:55 AM, Jean-François Brouillet wrote:
Hi.
I created an NSTableView and specified that the contents of each
of its NSTableColumn should hold instances of NSTextField. All
of this within IB.
I've set-up all the links everywhere (delegate + dataSource) the
upshot being that my controller method
- (void)
tableView: (NSTableView *) table
setObjectValue: (id) objectValue
forTableColumn: (NSTableColumn *) col
row: (int) row ;
is called.
If I do:
NSCell * cell = (NSCell *) [col dataCell] ;
I'm expecting cell to be an NSTextField instance.
My question is this:
At the time I am asked to change the contents of that specific
cell what difference should I be expecting to observe between
[cell stringValue]
and
[objectValue stringValue]
The reason I'm asking is because I'm getting a few "can't understand
selector"
messages, and I'm slowly narrowing down the possible causes.
Many Thanks
--
_______________________________________________
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