From: Vojtech Pavlik <vojtech@suse.cz>
To: Rob Landley <rob@landley.net>
Cc: linux-kernel@vger.kernel.org, Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: Spurious double-clicks in 2.6.0
Date: Tue, 30 Dec 2003 11:07:45 +0100 [thread overview]
Message-ID: <20031230100745.GA951@ucw.cz> (raw)
In-Reply-To: <200312292354.15084.rob@landley.net>
On Mon, Dec 29, 2003 at 11:54:14PM -0600, Rob Landley wrote:
> I recently had the opportunity to compare 2.6 and 2.4 on my thinkpad, and
> although most things are greatly improved in 2.6, one thing stands out.
>
> When I click on things in 2.6, about 1% of the time it double-clicks instead.
> (Clicking on a titlebar to raise the window causes it to roll up instead,
> clicking on a scrollbar causes it to page down twice instead of once, etc.
> I'm always afraid that pulling up the top left window menu (to move it to
> another desktop, make it always on top, etc) will kill the window instead...)
>
> This just doesn't happen under 2.4: I used the default kernel of Fedora Core 1
> for several days after a recent reinstall before putting 2.6 back on the box.
> But the input core doesn't seem to have this detail yet.
>
> In 2.4 there seems to be some minimum time required between clicks to count as
> a double-click, which nicely filters out this kind of suprious electrical
> contact bounce thing. (This makes sense: a human being simply CAN'T click
> twice within 1/20th of a second. The mouse driver should drop a second click
> that comes faster than that: it's keybounce from the previous click.)
Reconfigure X only to use one mouse source (either /dev/psaux or
/dev/input/mice, not both). Since in 2.6 the mouse inputs are already
mixed in the kernel for these two devices, X then gets all the data
twice, resulting in random doubleclicks.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
prev parent reply other threads:[~2003-12-30 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 5:54 Spurious double-clicks in 2.6.0 Rob Landley
2003-12-30 10:07 ` Vojtech Pavlik [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031230100745.GA951@ucw.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox