Bug#634272: fvwm: double-clicks with the touchpad left button not always taken into account

2011-08-12 Thread Vincent Lefevre
tags 634272 wontfix
close 634272
thanks

On 2011-08-11 17:50:30 +0100, Thomas Adam wrote:
 Regardless, this isn't going to change; and as I've been saying all along,
 increasing the value of ClickTime is exactly all that's required -- so in
 that regard, you're welcome.  :)

Well, I feared of about some drawbacks. For instance, with some
software, a press+drag immediately followed by a click makes
the click seen as the double click, and this is quite annoying.
However I couldn't find any drawback with fvwm (at least for
the moment).

Still, I would prefer the normal behavior. But if you say that
this isn't going to change, let's close the bug as wontfix.

BTW, shouldn't the default ClickTime value be increased from 150
to 200, in case other users would be affected by the same problem?

-- 
Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/
100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#634272: fvwm: double-clicks with the touchpad left button not always taken into account

2011-08-12 Thread Thomas Adam
Hi,

On 12 August 2011 15:40, Vincent Lefevre vinc...@vinc17.net wrote:
 BTW, shouldn't the default ClickTime value be increased from 150
 to 200, in case other users would be affected by the same problem?

No, but I will add an entry to the FAQ which will address this.

Thanks.

-- Thomas Adam



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#634272: fvwm: double-clicks with the touchpad left button not always taken into account

2011-08-11 Thread Thomas Adam
Vincent,

This is not a bug.  Please go and read about ClickTime, and then adjust it
accordingly.

-- Thomas Adam

-- 
Deep in my heart I wish I was wrong.  But deep in my heart I know I am
not. -- Morrissey (Girl Least Likely To -- off of Viva Hate.)



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#634272: fvwm: double-clicks with the touchpad left button not always taken into account

2011-08-11 Thread Vincent Lefevre
On 2011-08-11 12:32:30 +0100, Thomas Adam wrote:
 This is not a bug. Please go and read about ClickTime, and then
 adjust it accordingly.

I'll have to try to see if this changes anything. I remember having
increased DoubleClickTime to several seconds, with no differences.

Still if the click time is not accurate at that point, there is a
bug somewhere else. How is it computed?

-- 
Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/
100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#634272: fvwm: double-clicks with the touchpad left button not always taken into account

2011-08-11 Thread Thomas Adam
On 11 August 2011 12:52, Vincent Lefevre vinc...@vinc17.net wrote:
 On 2011-08-11 12:32:30 +0100, Thomas Adam wrote:
 This is not a bug. Please go and read about ClickTime, and then
 adjust it accordingly.

 I'll have to try to see if this changes anything. I remember having
 increased DoubleClickTime to several seconds, with no differences.

DoubleClickTime != ClickTime.  DoubleClickTime is to do with menus
only.  You want *ClickTime*.

The reason I'm telling you this is for two reasons:

1.  You mentions it happens with any + D action which means it can
only be clicktime related.
2.  Touch pads have a notorious habit of being over-sensitive in that
they'll often send two clicks in very rapid succession -- much more so
than a standard mouse, which again is likely why you're seeing it
specifically with a touchpad.

 Still if the click time is not accurate at that point, there is a
 bug somewhere else. How is it computed?

It's computed by taking the time between two single clicks in
succession, since X11 does not have a concept of double-click at all.

-- Thomas Adam



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#634272: fvwm: double-clicks with the touchpad left button not always taken into account

2011-08-11 Thread Vincent Lefevre
On 2011-08-11 12:58:32 +0100, Thomas Adam wrote:
 2.  Touch pads have a notorious habit of being over-sensitive in that
 they'll often send two clicks in very rapid succession -- much more so
 than a standard mouse, which again is likely why you're seeing it
 specifically with a touchpad.

OK, I've done some tests with both xev and fvwm and I think I now
understand what happens. First, xev shows that with the touchpad
button, the button release event can occur quite early (BTW, that's
why one can do a double-click with a touchpad button without releasing
the button completely). Moreover, after doing tests with fvwm, it
seems that for the double-click time threshold (ClickTime), fvwm
considers the time between the first button release event and the next
button press event, instead of the time between the two button press
events. Hence the problem.

Increasing the ClickTime value seems to solve the problem, but I now
wonder why fvwm considers the release-press time instead of the
press-press time like GNU Emacs and Firefox (and applications on other
systems, such as Mac OS X), for instance. Having a double-click that
behaves in a different way across different software is a bit annoying.
IMHO, this is the real problem... unless there's a good reason to do
things differently.

  Still if the click time is not accurate at that point, there is a
  bug somewhere else. How is it computed?
 
 It's computed by taking the time between two single clicks in
 succession, since X11 does not have a concept of double-click at all.

This is not what I was asking. But I've found the answer (see above).

-- 
Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/
100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#634272: fvwm: double-clicks with the touchpad left button not always taken into account

2011-08-11 Thread Thomas Adam
On Thu, Aug 11, 2011 at 05:18:08PM +0200, Vincent Lefevre wrote:
 Increasing the ClickTime value seems to solve the problem, but I now
 wonder why fvwm considers the release-press time instead of the
 press-press time like GNU Emacs and Firefox (and applications on other

Because it's also used to determine button press events, and moving the
mouse as well, as those are two actions that can also happen within an FVWM
function on the same button press.

There's also a larger historical reason to do with older/other XServers.

Regardless, this isn't going to change; and as I've been saying all along,
increasing the value of ClickTime is exactly all that's required -- so in
that regard, you're welcome.  :)

-- Thomas Adam

-- 
Deep in my heart I wish I was wrong.  But deep in my heart I know I am
not. -- Morrissey (Girl Least Likely To -- off of Viva Hate.)



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#634272: fvwm: double-clicks with the touchpad left button not always taken into account

2011-07-18 Thread Vincent Lefevre
Package: fvwm
Version: 1:2.5.30.ds-1
Severity: normal

I have in my config file:

AddToFunc Raise-and-MoveC Raise
+   M Raise
+   M Move
+   D RaiseLower

Mouse 1 T   A   Raise-and-Move

But when I double-click on the title-bar with the left button of the
touchpad while the window is raised, it is not always lowered. This
problem occurs quite frequently and is easy to reproduce (sometimes
several times in a row).

What's strange is that with the other left button of my laptop (the one
associated with the point stick), I never have this problem. I've thought
of a possible hardware or driver problem, but xev shows no noticeable
differences between these two left buttons when I double-click on them.

Note: when the window is already lowered, it is always raised when I
double-click on the title-bar, but this is due to C Raise; indeed
if I change the function to

AddToFunc Raise-and-Move   D RaiseLower

then the problem also occurs when the window is already lowered (i.e.
it is not always raised).

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages fvwm depends on:
ii  libc6   2.13-10  Embedded GNU C Library: Shared lib
ii  libcairo2   1.10.2-6 The Cairo 2D vector graphics libra
ii  libfontconfig1  2.8.0-3  generic font configuration library
ii  libfreetype62.4.4-2  FreeType 2 font engine, shared lib
ii  libfribidi0 0.19.2-1 Free Implementation of the Unicode
ii  libglib2.0-02.28.6-1 The GLib library of C routines
ii  libgtk2.0-0 2.24.4-3 The GTK+ graphical user interface 
ii  libice6 2:1.0.7-2X11 Inter-Client Exchange library
ii  libncurses5 5.9-1shared libraries for terminal hand
ii  libpng12-0  1.2.46-1 PNG library - runtime
ii  libreadline66.2-2GNU readline and history libraries
ii  librplay3   3.3.2-13 rplay network audio system - share
ii  librsvg2-2  2.34.0-1 SAX-based renderer library for SVG
ii  libsm6  2:1.2.0-2X11 Session Management library
ii  libstroke0  0.5.1-6  mouse strokes library -- runtime f
ii  libx11-62:1.4.3-2X11 client-side library
ii  libxcursor1 1:1.1.12-1   X cursor management library
ii  libxext62:1.3.0-3X11 miscellaneous extension librar
ii  libxft2 2.2.0-3  FreeType-based font drawing librar
ii  libxinerama12:1.1.1-3X11 Xinerama extension library
ii  libxpm4 1:3.5.9-1X11 pixmap library
ii  libxrender1 1:0.9.6-2X Rendering Extension client libra
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages fvwm recommends:
ii  fvwm-icons  20070101-1   icon *.xpm files from fvwm develop
ii  libx11-protocol-perl0.56-2   Perl module for the X Window Syste
ii  perl-tk 1:804.029-1.1+b1 Perl module providing the Tk graph

Versions of packages fvwm suggests:
ii  cpp   4:4.6.1-2  GNU C preprocessor (cpp)
pn  fvwm-themes   none (no description available)
ii  m41.4.16-1   a macro processing language
ii  menu  2.1.45 generates programs menu for all me
pn  wm-icons  none (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org