On Tue, 11 Aug 1998, Bob Woodside wrote:
>
> 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.
You have a point here. The thing is that it is very easy to click on window titlebar
buttons because they are always in reach. So, for something I use so often as that I thought
a button binding would be OK. With my 4 buttons per window I can do 12 different things, so
really, I do have buttons to spare, and though not as intuitive as having this option in a menu,
it is much quicker.I prefer to use menus for applications instead (eg, pine, netscape, xxgdb, xclock,
xbiff, top, rsh, ftp, etc...)
>
> > 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.
Your suggestion is very neat and would probably do for now. It would be nice though
to be able to keep everthing in one file and not in a .fvwm2rc and a .sh file.
Thanks for your help,
Neil
--
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 - 06:27:47 BST