On Sun, 25 Mar 2018 18:37:21 +0100 Thomas Adam <tho...@xteddy.org> wrote: > Hi, > > I'm afraid, despite all the suggestions mentioned, that I can't reproduce > this problem. >
I am not able to reproduce the bug, but I can reproduce what I think the behavior is. Consider the following keybinding Mouse 1 A SCM Raise Then use the binding to raise a window. If you hold down the mouse button, the Raise doesn't happen until after the release. While the mouse button is held down fvwm seems to be in a semi frozen state, as if it is waiting for the release event. While holding down the button (hold it for a couple of minutes), nothing in fvwm is updated, focus is not changed as I move the mouse around with SloppyFocus, other key bindings do not work, FvwmButtons ActiveColorsets do not change when hovered above them, and so on. But as soon as the release happens things go back to normal. Due to the info from the original reporter about timing between the press and release events, it appears that if the release event happens so quickly after the press event, that by the time fvwm starts to wait for a release event, the event has already happened. And it isn't until another click (which causes a release event) that fvwm then raises the window and continues on. Anyways, I think the cause of this bug is bad hardware, since it seems only this one laptop touchpad seems to produce press/release events so quickly to get fvwm stuck in such a state. jaimos
