On 20 Mar 2002 23:16:56 +0100, Dominik Vogt wrote:
>
> On Wed, Mar 20, 2002 at 09:40:41PM +0000, Mikhael Goikhman wrote:
> > Somewhere in your config file you said you want such automatical raising.
> > ClickToFocusRaises or MouseFocusClickRaises.
> >
> > What you described is one of the reasons I personaly don't use these
> > options, they just do not do what you want. Because sometimes you want a
> > window to be raised and sometimes not, so the solution is the explicit
> > raising, not automatic.
>
> So, how should it behave to satisfy your needs, Mikhael? Would a
> configurable raise button help? Or perhaps if only button 1
> raises (hard coded)?
No, automatical raising will never satisfy my needs. I like this:
Click never automatically raises a window.
Alt + click-2 RaiseLower a window.
Click on decorations raises
Alt-F5 RaiseLower
There is no reason for me why mouse buttons _inside_ a window should raise
just because I copy (mouse 1), paste (mouse 2) or open a context menu in
some apps (mouse 3). :)
But I probably would add a binding for my side mouse button number 8:
Mouse 8 WIFS M MoveOrRaiseLower
I even know how to patch FVWM (add one "0 && ") so that it does not
throw <<ERROR>> Illegal mouse button. But as I said Alt works ok for me.
Regards,
Mikhael.
--
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 Wed Mar 20 2002 - 16:57:05 GMT