Hi Doug, Yep, right place to ask FVWM questions. A meaningful subject line would be appreciated in future though.
> First issue: when you bind a mouse button with "Mouse <X> A A <Command>" > the binding should be active -everywhere- correct? Windows, Root, etc. > It should work, yes? Correct. The only caveat is window-specific bindings which will be available in 2.5.12 (when it comes out). Not as issue for you here though. > Also, if the mouse happens to be over a window when > the bound button is clicked should the resulting event be intercepted, > or interpreted and then passed on? It is never passed on. It is always intercepted/interpreted by FVWM. > Mouse 6 A A SendToModule FvwmProxy ShowToggle > > This binding seems to work in that when I click button 6 FvwmProxy comes > up no matter where I am. However, if I click button 6 over a window it > seems the event is being intercepted (FvwmProxy does come up) but it is > also being passed to the window below . FVWM will intercept the *ButtonPress* event. The *ButtonRelease* event will still go through to the application in the underlying window. Could this be causing your problem? > I'm just curious if > this is the "correct" behavior for such a binding. Yup. Binding to release events is a whole other can of worms. Suffice to say it is currently impossible in FVWM. SCoTT. :) -- 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 [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
