On Wed, Jul 24, 2002 at 05:21:00AM +0000, Mikhael Goikhman wrote: > On 23 Jul 2002 15:21:39 +0200, Dominik Vogt wrote: > > > > Raising windows: > > > > 8a) Raise when client window is clicked > > 8b) Raise when client window is clicked and window is unfocused > > 9a) Raise when decorations are clicked > > 9b) Raise when decorations are clicked and window is unfocused > > > > Recyclicng raise/focus clicks: > > > > 10) Pass focus clicks to application > > 11) Pass raise clicks to application > > 12) Allow bindings on focus clicks > > 13) Allow bindings on raise clicks > > > > Configuring the buttons to use: > > > > 14) Buttons to use for raise/focus clicks > > 15) Modifiers to use for raise/focus clicks > > Why not just replace 14 and 15 with 8=off, 9=off, 12=on, 13=on and real > Mouse bindings that do Focus or Raise or both?
Yes, that is very desirable. How about this: FocusClick 1 w m raise-and-focus FocusClick is roughly doing the same as Mouse, but kept separately for the special treatment it needs. We'd have to grab the mouse/ modifier combination from the binding only so that other clicks get passed to the client without interference from fvwm. I'm not sure about the function that is triggered. Raising and focusing can't just be run from a complex function (or as a built in command) because the client gets confused. > I already do this. I.e. my Alt-Mouse2 RaiseLowers. Mouse6 Raises, Mouse7 > slowly RaiseLowers (6 and 7 is the second wheel). > > I don't think many people will benefit the new mixed possibilities. > But the code will be more clean after you touch it, I am sure. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
