Sektor van Skijlen <ethouris@guess.if.gmail.com.is.valid.or.invalid> wrote:
[snip]
>I can't check it out on X, but looxlike on Windows it also does not depend on
>the double click interval settings for mouse.
>
>I'm developing "initial scratches" for a GUI library in C++. I try to use Tk
>as a basis for good ideas.
>
>I try to find appropriate approach for multi-clicks. As various systems allow
>a user to change the double-click interval, I consider using this value for
>the time interval. Despite that the time interval of 500 ms is good for most
>users and I hardly saw anyone changing it.
For X, the Xserver is not involved in any way with multi clicking. It
only delivers single click events to applications, and it is the
application (and its GUI libraries) that must figure out that a double
click occurred. The resource setting provides a hint on how to do
that.
For Windows, the GUI engine delivers the single click messages. As
well, it also synthesizes double click messages based on the time
between single clicks. As you have observed, the interval is a
globally set value.
Tk only looks at the single click messages (the only ones that exist
on X, and always available on Windows). It then synthesizes multi
click behaviour, based on the fixed 500 ms value.
The default value for Xt seems to be 200 ms, while for Windows it's
500 ms. I personally find 200 ms too short -- I occasionally have to
redo a double click, and triple clicks are downright difficult. This
might be the reason that Tk "just uses" 500.
If you are doing a complete GUI (in C++), then theoretically you have
considerable latitude in the "look and feel" aspects. You might be
able to design out the need for multi clicking, since it is a clumsy
interface for humans. We've come a long way since the days of the
single-button mouse :)
Received on Sun Apr 30 03:21:08 2006