Hi and thanks for your previous help, and sorry for the delay in replying. I thought I'd share my solution, which has nothing to do with hardware, in case someone else encounters the same issue:
The problem was that I had due to a bad merge I had two instances of the following function: AddToFunc "Raise/Move/Shade" + "M" Raise + "M" Move + "C" Raise + "D" WindowShade AddToFunc "Raise/Move/Shade" + "M" Raise + "M" Move + "C" Raise + "D" WindowShade And this was bound as follows: Mouse 1 TS A Function "Raise/Move/Shade" Apparently the "double" execution caused the behavior that I was seeing. Thanks a lot in any case for your suggestions, that put me on the right track! Regards, On Sat, Jun 4, 2022 at 7:26 PM David Fries <da...@fries.net> wrote: > > > I have a weird problem on my laptop > > I would also be asking on the hardware side. You mentioned releasing > a mouse button after dragging a window. Is this a physical button on > a USB mouse, or a physical button on touch pad, or a touch pad with a > down, up, down, drag motion? Especially the last I've seen touch pad > behavior where a drag to the edge will lock the drag down for you to > reposition your finger to continue the drag. That sounds like the > behavior you are describing, in which case has nothing to do with > fvwm, look at the touchpad settings to see if you can change it if you > want to, or just have an explanation. > > On Mon, May 30, 2022 at 09:15:50AM -0600, Jaimos Skriletz wrote: > > On Mon, May 30, 2022 at 12:27 AM Dov Grobgeld <dov.grobg...@gmail.com> > > wrote: > > > > > > Hello, > > > > > > The problem is that when I drag a window and then release the mouse > > > button, the dragging does not stop. It only stops after clicking the > > > mouse button one more time. > > > > > > Thanks in advance for any ideas. > > > > Two thoughts. First check (share) the mouse binding you use for > > clicking on the title bar and moving your windows. If the mouse > > binding calls Move directly, such as, 'Mouse 1 T A Move', that is the > > behavior you get, first click moves, second click releases. In this > > case you'll need to use a custom function (check the > > default-configuration for what it does), and that custom function > > needs to use '+ M Move' so the move is triggered by a mouse hold/move > > and then released by a mouse release. (You could also just check the > > default-configuration to see if this same behavior is there to inform > > you it is due to your configuration). > > > > My second thought is this could be hardware related. If the > > default-configuration has this same behavior then check xev and make > > sure you see both the ButtonPress followed by the ButtonRelease event. > > > > jaimos > > -- > David Fries <da...@fries.net>
