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 it caused a kernel panic.

Try setting both the table view's dataSource and delegate to nil before you set them to the new values. Then, of course, -reloadData. Just joking about the kernel panic. Although they've gotten much better since 10.2 and 10.3, table and outline views have been kind of snarky. These suggestions are the "best practices" which I see in my code.

If that doesn't work, delay some of those messages using - performSelector:withObject:afterDelay:, using a delay of .001. The idea is just to get the run loop to cycle.

If all that doesn't work, I'd look at the split view. I understand those can be kind of snarky too.

_______________________________________________

Cocoa-dev mailing list ([email protected])

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 [EMAIL PROTECTED]

Reply via email to