On Mon, Mar 01, 2004 at 09:52:08PM +0100, Uwe Pross wrote:
> Hi there,
>
> I have got the following mouse binding:
>
> Mouse 1 T A Function MoveOrRaiseOrLowerFunc
>
> If I define MoveOrRaiseOrLowerFunc as
>
> DestroyFunc MoveOrRaiseOrLowerFunc
> AddToFunc MoveOrRaiseOrLowerFunc
> + I ThisWindow (!Raised) Raise
> + C TestRc (NoMatch) Lower
> + M Move
> + D Maximize 100 100
>
> or
>
> DestroyFunc MoveOrRaiseOrLowerFunc
> AddToFunc MoveOrRaiseOrLowerFunc
> + I Current (!Raised) Raise
> + C TestRc (NoMatch) Lower
> + M Move
> + D Maximize 100 100
>
> the window can only be moved/maximized if it was raised.
>
> The definiton
>
> DestroyFunc MoveOrRaiseOrLowerFunc
> AddToFunc MoveOrRaiseOrLowerFunc
> + C ThisWindow (!Raised) Raise
> + C TestRc (NoMatch) Lower
> + M Move
> + D Maximize 100 100
> works as expected but raising/lowering is a bit delayed
Because fvwm has to wait until it's clear whether the action is a
click or double click. Either you have to get used to it or live
without double click bindings.
> and
> the window may be moved or maximized and the window is
> lowered.
>
> Any hints how to achieve the desired behaviour?
Works now.
Ciao
Dominik ^_^ ^_^
--
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 Tue Mar 02 2004 - 05:24:43 GMT