Thanks for the suggestions ...
Try setting both the table view's dataSource and delegate to nil
before you set them to the new values.
no help
If that doesn't work, delay some of those messages using -
performSelector:withObject:afterDelay:, using a delay of .001.
no help
On Nov 12, 2008, at 9:45 AM, David Blanton wrote:
Thanks for the suggestions ...
Try setting both the table view's dataSource and delegate to nil
before you set them to the new values.
no help
If that doesn't work, delay some of those messages using -
On Nov 12, 2008, at 11:45 AM, David Blanton wrote:
Thanks for the suggestions ...
Try setting both the table view's dataSource and delegate to nil
before you set them to the new values.
no help
If that doesn't work, delay some of those messages using -
Are you also calling -reloadData as suggested?
YES
David Blanton
___
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
The problem was in NSSplitVew and how it handles multiple subviews.
I do not know exactly what that problem was.
The original design was a 'placeholder view' as one side of the
splitview. To this placeholder view I programatically added a view
(built in IB) that had a custom view and
I have a table view which is contained in a split view
I set the data source for the table view
numberOfRowsInTableView is called
tableView:objectValueForTableColumn:row is called for each row.
later I change the data source.
numberOfRowsInTableView is called
On 2008 Nov, 11, at 13:53, David Blanton wrote:
I have a table view which is contained in a split view
later I change the data source.
Danger! Danger!
numberOfRowsInTableView is called
tableView:objectValueForTableColumn:row is never called
Whew. I thought you were going to say
