On 10-Aug-98 Neil Zanella wrote:
> I have bound the FvwmAuto autoraise module to all window's titlebar button #2
> mouse button #2, and I think it's handy because I use the module quite often.
>
> Since I am equally likely to use the module as to get fed up of it while
> running
> fvwm2, I also bound a function that kills the module to button #2 mouse
> button #3, 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.
Hmmm. I'd think that this would be better put in your top level menu,
or in a button bar - though I can sympathize if you don't want your desktop
cluttered with button bars and such; I only bring my button bar up on
special occasions. Logically, it would seem more appropriate to bind
window-specific things to the window decorations. But, that's your choice.
> This I think requires some sort of conditional structure in defining an
> Fvwm function which I don't think is present in Fvwm right now.
> So, could this functionality perhaps be added in the future?
Possibly, but a revised Fvwm command language is probably a good
bit in the future. Instead of waiting around for that, why not try a bit
of ingenuity? You can do what you want with a little shell script that
interacts with Fvwm via FvwmCommand. Here's how you do it.
First, bind whatever you like to a function you define in your
fvwm2rc, something like
AddToFunc ToggleAutoFunc
+ "I" Module FvwmCommandS
+ "I" Exec exec MyToggleAutoScript
Next, you write MyToggleAutoScript in the language of your choice -
Bourne shell, Perl, Tcl, whatever. This script should
1. Wait till it sees FvwmCommandS active
2. Check whether FvwmAuto is active
3. If FvwmAuto is active, send a KillModule command via FvwmCommand
4. If it is not active, send a Module FvwmAuto command via FvwmCommand
5. Wait for a respectable interval, and use FvwmCommand to send
the command "KillModule FvwmCommandS"
(Of course, some people like to keep FvwmCommandS active all the time, which
would simplify the script, but why waste resources?)
I know it's fashionable to argue for a new Fvwm command language
that's a full programming language, but you'd be surprised what you can do
without that, using the facilities that exist now.
> ----
>
> 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 it looks as if one never clicked on anything while in fact an
> action was invoked.
Strange, mine do. I think it depends on what kind of buttons you're
using - a very flat looking button may not show much difference, if any, or
it could have to do with the color scheme you specify for the window
decorations - and I'm not sure what happens if you use mini-icon style
buttons.
--
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 - 00:33:13 BST