Re: [Alphacocoa-devel] Command-double-click (RFC)

[Samuel L. <sam...@gm...>]

2017-04-21 16:45 GMT+02:00 <bde...@or...>:
>
> Hi all,
>
> I’d like to hear suggestions about Command-Double-Click.
>
> Traditionally in Alpha Command-double-clicking on a word
> triggers a mode-dependent behavior which generally
> amounts to searching a definition for the clicked word.
>
> But Command-clicking (single or double click) is used by
> most Mac applications to make a multiple selection:
> for instance, you select one portion of text then, while
> holding the command key, you select another
> (discontiguous) portion of text. You get a selection
> made of two or more pieces.
>
> So we get a contradiction: if Alpha’s traditional behavior
> is to be maintained, it becomes impossible to make
> a multiple selection by double-clicking (but is still possible
> by single-clicking-dragging-releasing the mouse).
>
> My suggestion would be the following: leave command-clicking
> (single or double) to multiple selections since users might
> be used to this common behavior and change Alpha’s traditional
> (but uncommon) behavior to Option-Command-Double-Click
> (i.e. add Option).
>
> Any suggestions ?

Yes! +1 to consistency with general MacOS user experience.

[ In the same spirit, I am relieved that in Alpha, pressing
backspace now deletes text backwards even when the
shift key is pressed (contrary to what happens in AlphaX).

In the Finder, Terminal, or any other app, backspace works
like that, deleting backwards whether or not the shift key
is pressed. This means that if you are keeping the shift key
pressed to type text in all capitals (I know shift-lock exists
but that's not the point), you can still press backspace to
delete backwards, without having to release the shift key.

I was always puzzled why AlphaX behaved otherwise.
If someone wants to set things up so shift-backspace
does something special, they can always do it, but in
my opinion we should not break common behaviour. ]