Re: NSTableView reloadData question FOLLOWUP
Re: NSTableView reloadData question FOLLOWUP
- Subject: Re: NSTableView reloadData question FOLLOWUP
- From: Andy Lee <email@hidden>
- Date: Wed, 10 Apr 2002 19:11:01 -0400
At 4:39 PM -0400 4/10/02, Bill Cheeseman wrote:
If the column headers are considered part of the table for purposes of
invoking a doubleAction, they should be considered part of the table for
purposes of making the table first responder.
I agree this is a bug, but my reasoning is slightly different. I
would say any part of a view that counts for purposes of _selection
or deselection_ should be considered part of the view for purposes of
making it first responder. Since columns can be selected by a click
on the header, _that_ (I would argue) is why the click should make
the table first responder.
A possible hair-split here might be that a table can be set to not
allow selectable columns. I might be tempted to argue that clicking
a column header should only make the table first responder if columns
are selectable.
I think of double-clickability as a separate issue, usually but not
necessarily correlated with first-respondability. To me, something
is double-clickable if you can "open" it in some sense, where opening
is conceptually different from selecting. DragThing allows settings
that illustrate this distinction. I admit it's hard to think of
other examples.
1. Shouldn't clicking a table's column headers or scroll bars make the table
first responder?
I would say yes to the headers (with the possible hair-split I
mentioned above) but no to the scroll bars. If I have a window with
two scrolling NSTextViews, I don't expect scrolling one to deselect
the other. In fact, that would be highly annoying.
when the table is empty, it responds only to double-clicks in the column
headers; double-clicks in the body of an empty table do not work. As soon as
there's at least one row visible in the table, double-clicking anywhere in
the empty part of the table's main body does work.
This seems weird to me and I would agree it's a bug. The empty part
of the body should behave the same regardless of the number of rows.
I can't see why zero would be a special case.
--Andy
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.