FVWM Bug Tracking notification
new message incoming/813
Message summary for PR#813
From: [EMAIL PROTECTED]
Subject: Dragging button 3 with FvwmPager
Date: Tue, 27 Nov 2001 06:23:21 -0600
0 replies 0 followups
====> ORIGINAL MESSAGE FOLLOWS <====
>From [EMAIL PROTECTED] Tue Nov 27 06:23:22 2001
Received: from karazm.math.uh.edu ([129.7.128.1])
by malifon.math.uh.edu with esmtp (Exim 3.20 #1)
id 168hGk-0005MW-00
for [EMAIL PROTECTED]; Tue, 27 Nov 2001 06:23:22 -0600
Received: from malifon.math.uh.edu (IDENT:[EMAIL PROTECTED] [129.7.128.13])
by karazm.math.uh.edu (8.9.3/8.9.3) with ESMTP id GAA16115
for <[EMAIL PROTECTED]>; Tue, 27 Nov 2001 06:23:21 -0600 (CST)
From: [EMAIL PROTECTED]
Received: from localhost ([127.0.0.1] ident=65534)
by malifon.math.uh.edu with esmtp (Exim 3.20 #1)
id 168hGj-0005MS-00
for [EMAIL PROTECTED]; Tue, 27 Nov 2001 06:23:21 -0600
To: [EMAIL PROTECTED]
Subject: Dragging button 3 with FvwmPager
Message-Id: <[EMAIL PROTECTED]>
Date: Tue, 27 Nov 2001 06:23:21 -0600
Full_Name: Guillaume Chazarain
Version: 2.4.3
CVS_Date:
OS:
X_Server: 4.1.0
Submission from: (NULL) (134.59.2.127)
In the FvwmPager manual page it is stated that :
---
Clicking mouse button 3 on a location will cause the viewport to move to
the
selected location and switch desks if necessary
---
Dragging button 3 will cause the viewport to move as you drag but not
switch desktops, even if the pointer moves to another desktop.
---
I don't understand what 'not switch desktops' means because it is the same
if I drag the button 3 or if I continually click it while moving the
mouse.
Another problem I have, is that sometimes (actually most of the times),
dragging the button 3 has the same effect as if I clicked it just once.
That is, the viewport is not smoothly moved.
I think I found where it comes from :
The dragging is activated if we are in a MotionNotify event and
(Event->xmotion.state == Button3MotionMask) but what I have on my system
is
(Event->xmotion.state == (Button3MotionMask | EnterWindowMask))
so the following patch fixes the problem for me.
I understand that the bug may not be in fvwm2 but in X or whatever, but
the
easiest solution for me was to fix it in fvwm2.
---
diff -u fvwm-2.4.3/modules/FvwmPager/x_pager.c
fvwm-2.4.3-button3pager/modules/F
vwmPager/x_pager.c
--- fvwm-2.4.3/modules/FvwmPager/x_pager.c Sun Sep 16 17:51:18 2001
+++ fvwm-2.4.3-button3pager/modules/FvwmPager/x_pager.c Fri Nov 23 22:42:18
2001
@@ -1156,7 +1156,7 @@
while(XCheckMaskEvent(dpy, PointerMotionMask |
ButtonMotionMask,Event))
;
- if(Event->xmotion.state == Button3MotionMask)
+ if(Event->xmotion.state & Button3MotionMask)
{
for(i=0;i<ndesks;i++)
{
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
