Re: [Q] doubleAction on a NSTableView misbehaving?
Re: [Q] doubleAction on a NSTableView misbehaving?
- Subject: Re: [Q] doubleAction on a NSTableView misbehaving?
- From: Quincey Morris <email@hidden>
- Date: Thu, 2 Apr 2009 11:34:34 -0700
On Apr 2, 2009, at 11:11, Eric Gorr wrote:
The documentation for setDoubleAction on a NSTableView states:
If the double-clicked cell is editable, this message isn’t sent
and the cell is edited instead.
However, the behavior I am seeing is that although my double-clicked
cell is editable (tableView:shouldEditTableColumn:row: does return
YES), the selector I passed to setDoubleAction is called when I
double click on the cell.
I can only edit the cell if I first click on the cell, pause for
about 1 second, and click again.
The fact that a double-click on an editable cell doesn't start an
edit when doubleAction has been assigned looks like a bug to me or
the documentation is wrong or I have misinterpreted something.
Anyone care to comment?
Yes, if I don't assign something to doubleAction and double click
the cell, I can edit.
From the Leopard developer release notes:
"NSTableView/NSOutlineView - Single click to editNSTableView and
NSOutlineView now behave like Finder and allow a single click to put
it into edit mode. This is done by calling -
hitTestForEvent:inRect:ofView: and checking if the cell returns
NSCellHitEditableTextArea. This allows you to set a doubleAction and
perform some different task when the doubleAction is invoked (for
instance, Finder opens files on a double click, and edits via a single
click). If the doubleAction is not set, editing is still allowed via a
double click."
_______________________________________________
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
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden