How did Snow Leopard kill my table view?
How did Snow Leopard kill my table view?
- Subject: How did Snow Leopard kill my table view?
- From: Bill Cheeseman <email@hidden>
- Date: Sat, 15 May 2010 19:39:48 -0400
I wrote an application that was built on and for Mac OS X 10.5 Leopard. The main view in its main window is a stock NSTableView. I used Cocoa bindings to populate and manipulate the table view. It works fine running on Leopard, but on Snow Leopard the table view no longer enables itself when I add the first piece of data to it.
What changed in Snow Leopard that would cause that to fail? I didn't actually set up the Enabled binding of the table view. The table view became enabled in Leopard due to some bindings-related interaction that I no longer recall and can't figure out. Perhaps it was because I called -addObject: on my NSArrayController to add the first object to the table.
I've been able to fix the problem the old-fashioned way, by creating an IBOutlet for the table view and calling -setEnable:YES on it explicitly at the right time. But there ought to be some way to enable the table view using bindings, and I'm frustrated that I can't find a way to do it. All help appreciated.
(Yes, I've read the Snow Leopard release notes and Googled the issue as far as I can take it. In case anybody wants to test it, the application is Event Taps Testbench 1.1 <http://prefabsoftware.com/uibrowser>.)
--
Bill Cheeseman - email@hidden
_______________________________________________
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