No, I was not intending to use that new Leopard feature. I guess you
are using the new NSCell method hitTestForEvent:inRect:ofView. I am
using Leopard (development and runtime, w 10.4u SDK), but just
subclassing TableView. When I disconnect the new TableView all except
the given column are editable. In fact the two clicks can be separated
by a long time or short. It does not matter if I moved the cursor
between the two clicks.
However I get the same behavior you mention when the subclassed-
TableView is hooked up. Double clicking with the mouse in the same
place does not edit the "editable" columns. If I move the cursor
between clicks It does edit. Sounds like a bug.
On Jan 20, 2008, at 11:49 PM, Jerry Krinock wrote:
On 2008 Jan, 20, at 9:14, John James wrote:
I subclassed TableView and called setDoubleAction: in
myTableView::awakeFromNib to a method which I do a special edit on
items a given column; All works fine for the column that I set
UNeditable;
According to the docs "If the double-clicked cell is editable, this
message isn’t sent and the cell is edited instead." In mine the
double-click action is always called even for the columns that have
been set editable.
I set all columns except the one I want the doubleAction to be
called, to editable in IB. What am I missing?
If I recall correctly, I believe that the "documentation" you are
referring to is the Mac OS 10.5 AppKit Release Notes, and you are
using the new "single-click to edit" feature in Leopard's NSTable/
OutlineView. Is that correct?
_______________________________________________
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
