Re: NSTableView apparently doesn’t respect allowsEmptySelection:NO anymore on Leopard
Re: NSTableView apparently doesn’t respect allowsEmptySelection:NO anymore on Leopard
- Subject: Re: NSTableView apparently doesn’t respect allowsEmptySelection:NO anymore on Leopard
- From: Stéphane Sudre <email@hidden>
- Date: Sat, 24 Nov 2007 14:29:46 +0100
On samedi, novembre 24, 2007, at 10:47 AM, Wdyp wrote:
Hello!
Has anyone else noticed that since Leopard NSTableView doesn’t respect
allowsEmptySelection:NO anymore?
Whether set in IB or programmatically, and setting the
NSArrayController avoidEmptySelection bit doesn’t help.
This happens in a project that is still working perfectly on Leopard
whenever built on Tiger.
My table view gets its content with a filterPerdicate binding that
returns no object and looses selection, when the predicate changes and
populates the table with some objects again, empty selection is
allowed, no object gets selected, forcing the user to click on an item
to select it.
Why is my project behaving differently from on Tiger?
Honestly, it might not be such as bad move. Because in Tiger and
earlier version, the behavior for this was quite buggy.
In many cases, the tableView:selectionDidChange: delegate callback was
not sent and you had to call it yourself.
_______________________________________________
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