Re: curious behavior of Conditionally Sets Enabled in NSTableView
Re: curious behavior of Conditionally Sets Enabled in NSTableView
- Subject: Re: curious behavior of Conditionally Sets Enabled in NSTableView
- From: Matt Neuburg <email@hidden>
- Date: Sat, 04 Mar 2006 17:42:22 -0800
- Thread-topic: curious behavior of Conditionally Sets Enabled in NSTableView
On Fri, 3 Mar 2006 14:46:58 -0800, Corbin Dunn <email@hidden> said:
>It sounds like it is setting the enabled state of the tableview. Note
>that NSTableView doens't really handle the enabled state all that
>well, and all it does is give up first responder status. It should be
>setting the enabled state of the cell or column. This may be a big;
>do you have a small test case that reproduces it, or is it only in
>your large app?
>-corbin
Yup, I can reproduce in a minimal app. Submitted to bugreporter (Bug ID#
4467230). m.
>On Mar 3, 2006, at 12:01 PM, Matt Neuburg wrote:
>
>> I have an NSTableView whose columns are bound through the
>> arrangedObjects of
>> an NSArrayController. The table view allows multiple selection.
>>
>> If I select a row of the table view, fine.
>>
>> If I then command-click another row of the table view, both rows are
>> selected, but the table view is then disabled (it loses focus and the
>> selected rows turn grey). This surprised me, and it wasn't what I
>> wanted, so
>> I set out to investigate further.
>>
>> If I then command-click *another* row of the table view, all three
>> rows are
>> selected and the table view is enabled.
>>
>> If I then command-click one of the three selected rows, two rows are
>> selected and the table view is enabled. So it is possible to select
>> exactly
>> two rows, but only in this roundabout way (enable three, then enable
>> two).
>>
>> This behavior goes away if I uncheck "Conditionally Sets Enabled".
>> Therefore
>> I conclude that it is *due* to "Conditionally Sets Enabled". But
>> what on
>> earth could be the logic of such behavior? What does "Conditionally
>> Sets
>> Enabled" imagine it is doing? What "condition" could it be thinking
>> of here?
>> It seems to me that this behavior is just plain buggy; it serves no
>> useful
>> purpose that I can envision. Should I file a bug, or there some
>> wonderful
>> thing going on here that I'm just not appreciating? m.
>>
>> --
>> matt n
>
>
>
>
--
matt neuburg, phd = email@hidden, <http://www.tidbits.com/matt/>
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
<http://www.amazon.com/gp/product/0596102119>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden