Insisting on metaphors that exploit the device's weaknesses (Re: Centralization of graphical awesomeness)

Matthias Huber matthias.huber at
Sat Oct 31 09:21:13 CET 2009

Carsten Haitzler (The Rasterman) schrieb:
> On Fri, 30 Oct 2009 19:47:27 +0100 Matthias Huber
> <matthias.huber at> said:
>> Laszlo KREKACS schrieb:
>>>> To not confuse with window changing, I would suggest the following
>>>> scenario:
>>>> 1. double click for launching an app
>>>> why double click ? for me, i am using double click for a menu and a single
>>>> click for starting the app.
>>> Because when sliding, you can have accidental clicks. I know it from
>>> the hard way.
>>> (I came up a nice usability workaround in paroli exactly for this
>>> issue. It works good.)
>> yes i know this also from paroli. but it is solvable i think.
>> openbox has a tunable parameter for distinguish between slide and click.
>> in my oppinion, this is highly usable.
>> i personally find a single click more elegant and usable than double click.
> the problem is not differentiating between slide and click - e and elementary
> have this too. it's that if you drag horizontally for example, your actual
> events often look something like:
> +----+ +--+ +--+   +-----+ +    +-+    + +------+ + +   +   +---+
that's exact what i told you, what openbox has: they say: if movement < 
number_pixels then its click,
if movement >= pixels, its slide.

in your case, one could hava a hysteresis over the time: if a single 
click comes shortly after a slide,
it is part of slide.

if you measure now the time of the tap, you have all you need for 
differentiating between all this three events.

generally i think, its better to get the btn-release instead of 
btn-down. (from the view of windowmanager)

and you are right: it should be done in tslib or window manager.

-------------- next part --------------
An HTML attachment was scrubbed...

More information about the community mailing list