Re: FVWM: FvwmAuto: bugs and suggestions

From: Tim Phipps <tim_at_quadrics.com>
Date: Tue, 11 Aug 1998 10:40:26 +0100

Neil Zanella wrote:
> .........., but to save buttons I would like button #2, mouse button #2 to
> activate the module if it is not running and deactivate it if it is running.

How about binding the following function to the button
AddToFunc ToggleAuto "I" FvwmAuto 500
+ "I" Exec shell_script_to_kill_FvwmAuto_if_more_than_one

The shell_script_t.... will depend on your operating system but can run
a ps, grep, wc to count the number of FvwmAuto modules running and kill
them all if there is more than one.

> Now, another thing, when I click on the button to activate the module the button
> does not seem to go down for 1/6 of a second or anything which looks bad cause

This might be the way you have written your functions causing fvwm to
wait for the ClickTime (150ms) to work out if you are clicking or
dragging. If you write your functions thus:

AddToFunc blahblah "I" whatever
+ "I" whatever

then fvwm will not wait for ClickTime and will do whatever immediately.
If you write them:

AddToFunc blahblah
+ "I" whatever
+ "I" whatever

it will wait even though you haven't got any "M", "C" or "D" lines in
the function.

Hope this helps,
Tim.
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Tue Aug 11 1998 - 04:44:46 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:38:01 BST