Hello,
It's my perception that the mouse-triggered actions behave inconsistently with what the manual says.
Specifically, actions don't seem to be triggered until a click is completed - not on mouse-down - which is what is suggested by the manual.
Take for example this quote from the fvwm man page:
"The name must not contain embedded whitespace. No guarantees are made whether function names with embedded whitespace work or not. This behavior may also change in the future without further notice. The letter before the action tells what kind of action triggers the command which follows it. 'I' stands for "Immediate", and is executed as soon as the function is invoked. 'M' stands for "Motion", i.e. if the user starts moving the mouse. 'C' stands for "Click", i.e., if the user presses and releases the mouse. 'H' stands for "Hold", i.e. if the user presses a mouse button and holds it down for more than ClickTime milliseconds. 'D' stands for "Double-click". The action 'I' causes an action to be performed on the button-press, if the function is invoked with prior knowledge of which window to act on."
This suggests that "Immediate" commands are executed on mouse-down, while "Click" type is for press-and-release.
I've noticed that Immediate commands are only exceuted after release or I press and move the pointer a bit. This is certainly not "Immediate" - and there is a definite need for commands to be executed on mousedown.
In fact, for all mouse-bindings, actions are excuted on click-and-release instead of mousedown. Key binding actions are executed on mouse-down.
And also - there is this entry in the FvwmButtons manpage:
"ActionOnPress ~~ Usually the action is executed on the button release except for the Popup action. This option changes this behavior, the action is executed on the button press. This may be good, for example, with Menu or SendToModule that generates popups, or when Frame is 0 and the button would look unresponsive otherwise."
This suggests that popup actions are executed on mousedown. This is not the case with buttons. They behave like "Immediate" commands - executing only on mousedown+movement or mousedown+release.
If I add ActionOnPress, actions behave like "Immediate" commands again - that is - not immediately!
Incidentally, popup menus only behave correctly in keybindings and mousebindings on the Root Desktop.
Can anyone shed some light on this issue? It's a major annoyance.
I now realize that it's somewhere within my configuration files that is causing this. The Sample95 configuration does not have this behavior.
My configuration files are based on fvwm-crystal. Any idea about what settings could cause this glitch?
-- Tommy C. Li | RealityMage Registered Linux User # 327563 | http://www.impulsestorm.com Gentoo Linux | Kernel: 2.6.8-rc2-love1 -- 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]
