Re: NSTableDataSource: objectValueForTableColumn Working but setObjectValue Passing Bad Parameters
Re: NSTableDataSource: objectValueForTableColumn Working but setObjectValue Passing Bad Parameters
- Subject: Re: NSTableDataSource: objectValueForTableColumn Working but setObjectValue Passing Bad Parameters
- From: Grant Erickson <email@hidden>
- Date: Tue, 24 Mar 2009 09:45:21 -0700
- Thread-topic: NSTableDataSource: objectValueForTableColumn Working but setObjectValue Passing Bad Parameters
On 3/24/09 9:20 AM, Grant Erickson wrote:
> However, I am finding that setObjectValue seems to be passing incorrect and
> unexpected parameters relative to those I receive in
> objectValueForTableColumn. From the console:
>
> tableView: 0x1281f0 objectValueForTableColumn: 0x129c00 (ID) row: 0
> tableView: 0x1281f0 objectValueForTableColumn: 0x12cfe0 (Active) row: 0
> tableView: 0x1281f0 objectValueForTableColumn: 0x1333b0 (Value) row: 0
> tableView: 0x1281f0 objectValueForTableColumn: 0x129070 (Status) row: 0
> tableView: 0x1281f0 objectValueForTableColumn: 0x137b60 (Path) row: 0
>
> That all seems correct following awakeFromNib in my application controller.
>
> tableView: 0x1281f0 setObjectValue: 0x129070 forTableColumn: 0x181530
> ((null)) row: -1854878728
> tableView: 0x1281f0 setObjectValue: 0x12cfe0 forTableColumn: 0x177b70
> ((null)) row: 41056
>
> It would seem that the object and column parameters are potentially swapped
> and the row parameter is just random data.
Regrets for the list spam. Sometimes stepping away and taking a walk are all
that are needed.
(Un)fortunately, this was due to a typo so glaringly obvious it was wasn't
until I stepped back, walked away and looked at it with fresh eyes. :-/
Regards,
Grant
_______________________________________________
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
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden