• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: curious behavior of Conditionally Sets Enabled in NSTableView
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: curious behavior of Conditionally Sets Enabled in NSTableView


  • Subject: Re: curious behavior of Conditionally Sets Enabled in NSTableView
  • From: Corbin Dunn <email@hidden>
  • Date: Fri, 3 Mar 2006 14:46:58 -0800

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



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

_______________________________________________ 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
References: 
 >curious behavior of Conditionally Sets Enabled in NSTableView (From: Matt Neuburg <email@hidden>)

  • Prev by Date: Re: Radio Button Matrix Bindings
  • Next by Date: Re: Advice on using NSCell
  • Previous by thread: curious behavior of Conditionally Sets Enabled in NSTableView
  • Next by thread: Re: curious behavior of Conditionally Sets Enabled in NSTableView
  • Index(es):
    • Date
    • Thread