Re: Touchscreen Compatibility [was: Feature proposal: combined system status menu]

[Piñeiro <apinheiro igalia com>]

On 04/30/2013 11:37 AM, Allan Day wrote:
> It should also be said that this pattern does have benefits when you
> are using a pointer. An obvious example of this is the difference
> between single/double click. Not only is double click not exactly
> ideal on a touchpad, but it is also used inconsistently and is
> non-discoverable (some places you need double click to open, others
> you need single.) In general, using single click consistently is a
> much better approach, especially when combined with discoverable
> mechanisms for selection.

FWIW, the one-click/double-click discussion is a really long-discussion.
In fact there are a 10 years bug still open about adding the possibility
to configure the behaviour. The good news news is that it seems that
there are recent activity on that bug [1].

Additionally, there is also a wiki page related with that:
https://live.gnome.org/SingleClickPolicyPlan

It was started with an accessibility-pov in mind, but as you are saying,
there are several other reasons to discuss about that. So just pointing
to avoid a disaggregated discussion.

About my personal opinion:
  * As others said, it is needed to have a consistent behaviour on the
platform.
  * If the consistent behaviour includes two-clicks for some situations,
it should be configurable, that is what the bug tries to solve.
  * Probably should be also configurable if a "only one-click" policy is
defined (but put more priority on the former).

Best regards

[1] https://bugzilla.gnome.org/show_bug.cgi?id=121113


-- 
Alejandro Piñeiro Iglesias