FROM : Wdyp
DATE : Thu Nov 29 23:41:39 2007
> What you are referring to is one of the primary reasons why single-
> click to edit is so beneficial for apps and users. You have some
> particular text in a cell that you want to be editable, yet at the
> same time you also want a doubleAction to do something else.
> Take Xcode for example; the project list
> supports a doubleAction (ie: open that file in a new window). Before
> Leopard, the only way to inline-edit was with a strange (and not
> easily discoverable) alt-click to begin editing the cell. On Leopard,
> it is much easier; you just single-click on the text (ala Finder) to
> begin editing.
>
> --corbin
Too bad I didn’t have this Xcode trick while I was on Tiger!!
Anyway, I find the single-click editing very slow: there is a
quite long delay before the single click actually has an effect
which is confusing for the user that might be tempted to double-click
instead! I guess this is to allow for an eventual drag operation start…?
> Side note: there is a way to disable the single-click editing
> behavior, however, it should be considered a last resort. Single-click
> editing is nice for consistency on Leopard, and apps that move away
> from that will make it more difficult for users to use that particular
> app (ie: your app).
>
> --corbin
I don’t agree completely: the users are big guys, many things behave
differently
in different apps.
For example, back in Tiger, the Finder’s and iTunes’ single-click were
the "inconsistent" behavior
and I found it confusing, especially in iTunes (as I mostly use a tab/
arrow-return sequence
to begin editing an item’s title in the Finder…).
For people coming from Tiger (not everyone is a msft switcher…) this
new feature is confusing,
especially as it is enforced in every Cocoa app, changing, without the
developer’s agreement,
the traditional behavior of apps they were used to.
The new inter-cell navigation is also quite confusing, I’ll probably
post about it, yelling for help.
Flofl._______________________________________________
Cocoa-dev mailing list (<email_removed>)
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:
http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
This email sent to <email_removed>
DATE : Thu Nov 29 23:41:39 2007
> What you are referring to is one of the primary reasons why single-
> click to edit is so beneficial for apps and users. You have some
> particular text in a cell that you want to be editable, yet at the
> same time you also want a doubleAction to do something else.
> Take Xcode for example; the project list
> supports a doubleAction (ie: open that file in a new window). Before
> Leopard, the only way to inline-edit was with a strange (and not
> easily discoverable) alt-click to begin editing the cell. On Leopard,
> it is much easier; you just single-click on the text (ala Finder) to
> begin editing.
>
> --corbin
Too bad I didn’t have this Xcode trick while I was on Tiger!!
Anyway, I find the single-click editing very slow: there is a
quite long delay before the single click actually has an effect
which is confusing for the user that might be tempted to double-click
instead! I guess this is to allow for an eventual drag operation start…?
> Side note: there is a way to disable the single-click editing
> behavior, however, it should be considered a last resort. Single-click
> editing is nice for consistency on Leopard, and apps that move away
> from that will make it more difficult for users to use that particular
> app (ie: your app).
>
> --corbin
I don’t agree completely: the users are big guys, many things behave
differently
in different apps.
For example, back in Tiger, the Finder’s and iTunes’ single-click were
the "inconsistent" behavior
and I found it confusing, especially in iTunes (as I mostly use a tab/
arrow-return sequence
to begin editing an item’s title in the Finder…).
For people coming from Tiger (not everyone is a msft switcher…) this
new feature is confusing,
especially as it is enforced in every Cocoa app, changing, without the
developer’s agreement,
the traditional behavior of apps they were used to.
The new inter-cell navigation is also quite confusing, I’ll probably
post about it, yelling for help.
Flofl._______________________________________________
Cocoa-dev mailing list (<email_removed>)
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:
http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
This email sent to <email_removed>
| Related mails | Author | Date |
|---|---|---|
| Manfred Schwind | Nov 26, 16:00 | |
| j o a r | Nov 26, 16:47 | |
| Stephane Sudre | Nov 26, 18:13 | |
| Corbin Dunn | Nov 28, 01:52 | |
| Manfred Schwind | Nov 29, 12:37 | |
| Corbin Dunn | Nov 29, 17:35 | |
| Wdyp | Nov 29, 23:41 | |
| Corbin Dunn | Nov 30, 02:07 | |
| Mike Wright | Dec 1, 12:47 | |
| Corbin Dunn | Dec 3, 21:55 | |
| john chen | Mar 20, 22:32 | |
| john chen | Mar 21, 17:47 |






Cocoa mail archive

