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: Corbin Dunn <email@hidden>
- Date: Tue, 27 Nov 2007 16:59:12 -0800
On Nov 24, 2007, at 1: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?
This simply sounds like a bug, however, there may be a very valid
reason why this change happened. I can't say for sure without looking
at code for it. Please log a bug, and if you have time, create a
sample program that illustrates the problem (that will greatly speed
up the process of finding what is wrong and possibly getting it fixed).
For the time being, I'd suggest making sure the selection is
maintained yourself whenever the filter changes.
--corbin_______________________________________________
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