On Mon, Mar 17, 2003 at 12:04:44AM -0500, Ben Winslow wrote:
> I updated my CVS tree a couple of days ago, and since then, whenever I
> call Move from a mouse binding, the command doesn't happen until after I
> release the mouse button.
>
> The binding in question is:
> Mouse 1 W 3 Move
>
> The old behavior was to start moving on click, and stop moving when the
> mouse was released. I know there was some mumbling about commands
> related to mouse presses, but the messages I could find weren't quite
> related--forgive me if I missed something.
I see, this change is not going to make me happy.
BEGIN THEORY
For some reason, a more or less random number of commands worked
on button press while other commands worked on button release.
The first type did not work when invoked outside a window context,
for example on the root window:
mouse 3 a sc move
just flashed the selection cursor, selected the root window and
beeped. The right way to have move-on-press is
AddToFunc move_on_press
+ I Move
mouse 1 W 3 function move_on_press
In the future, I would like to remove the difference between both
types of commands.
END THEORY
So much for the theory. Unfortunately, many people rely on the
old, broken behaviour. It should be relatively easy to write a
script that changes your config, though.
Bye
Dominik ^_^ ^_^
--
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 Mon Mar 17 2003 - 04:01:23 GMT