On Fri, Feb 18, 2000 at 09:33:10AM +1100, siegfried_at_colonial.com.au wrote:
> i think i've sussed this just by pure chance! it looks as though fvwm is
> waiting for the (absence of the) second click before it can decide what it
> is to do. i've noticed that certain functions seem to take a while for no
> readily apparent reason. then i was playing around with the following:
>
> Mouse 1 WTFSI SC Move-or-Lower
> Mouse 3 WTFSI SC Move-or-Raise
>
> AddToFunc Move-or-Raise
> + "I" Raise
> + "M" Move
> + "D" Lower
>
> AddToFunc Move-or-Lower
> + "C" Lower
> + "M" Move
>
> and i noticed that the mb3 function waits while mb1 is immediate - curious.
> looking at the above the only thing i can imagine is that fvwm has to wait
> for the double click timeout to expire to be sure whether it's a single or
> double click. i hope someone can confirm this?
Exactly. BTW, the delay only occurs if you hold the button but
don't start moving. So, although the cursor doesn't change to the
move cursor, you can still start moving the window.
Bye
Dominik ^_^
--
Dominik Vogt, Agilent Technologies, Dept. BVS
Herrenberger Str.130, 71034 Boeblingen, Germany
phone: 07031/464-4596, fax: 07031/464-3883, dominik_vogt_at_agilent.com
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Fri Feb 18 2000 - 02:41:50 GMT