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 13:00:59 -0700
On Apr 2, 2009, at 12:28, Eric Gorr wrote:
So, it doesn't seem possible to, for example, avoid have the
doubleAction invoked if -hitTestForEvent:inRect:ofView: returns
NSCellHitEditableTextArea.
I would still like the edit to start if the user double-clicks on
the editable part of the cell, but the doubleAction invoked if they
do not.
I have a cell consisting of an image and some text. This cell is a
subclass of NSTextFieldCell.
a. If your cell class is intended to be perceived by the user as a
kind of text field, then it would be highly desirable from the
usability point of view to make its behavior consistent with regular
text fields that have double-click actions (e.g. the Finder case or
the Xcode case). (And, if you don't mess with it, the behavior will
vary "properly" according to whether your app is running on Tiger or
Leopard.) It might be more annoying to a user to have to figure out
where to click to get the desired behavior than it would be to have to
learn the click-wait-click gesture that replaces double-click for
editing.
b. If you must use the behavior you're proposing, you might be able to
invoke setDoubleAction: every time from within
hitTestForEvent:inRect:ofView: to choose the correct behavior based on
the hit test.
_______________________________________________
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