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: Corbin Dunn <email@hidden>
- Date: Mon, 6 Mar 2006 13:32:34 -0800
On Mar 4, 2006, at 5:42 PM, Matt Neuburg wrote:
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.
Your demo app has a bug in it; the "Conditionally sets enabled"
binding is set for the doubleClickArgument/target binding(s). Removing
them makes it work fine. Having them there makes it work as expected;
a disabled tableview on 10.4 will refuse first responder status.
Conditionally sets enabled is working; initially I thought you had
only set it on the tablecolumn, based on your description. The column
shouldn't affect the table's enabled/disabled state.
thanks,
corbin
_______________________________________________
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