public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Valdis.Kletnieks@vt.edu
Cc: Joshua Kwan <joshk@triplehelix.org>,
	linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: 2.6 input drivers FAQ
Date: Mon, 2 Feb 2004 21:18:13 +0100	[thread overview]
Message-ID: <20040202201813.GA272@ucw.cz> (raw)
In-Reply-To: <200402021812.i12IC6eR006637@turing-police.cc.vt.edu>

On Mon, Feb 02, 2004 at 01:12:06PM -0500, Valdis.Kletnieks@vt.edu wrote:

> Section "InputDevice"
>         Identifier  "Mouse0"
>         Driver      "mouse"
>         Option      "Device" "/dev/psaux"
>         Option      "Protocol" "ExplorerPS/2"
>         Option      "Buttons" "7"
>         Option      "Emulate3Buttons" "on"
>         Option      "ZAxisMapping" "6 7"
> EndSection
> 
> And if I *had* gotten it in there twice, why would it only hit sporadically
> once or twice a day, as opposed to *all* mouse events (clicks, moves,
> etc) being doubled?

Because normally the X server reads them in very quick succession and if
you don't make a very short click, the sequence looks like this:

push1 push2 release1 release2, which is fine, because X interprets that
as just a push and a release.

If there is disk activity or something else that causes the scheduling
to be delayed, it's push1 release1 push2 release2, which counts as a
doubleclick.

Hence sporadic doubleclicking.

For movement, of course, you get twice the mouse speed, but usually most
people just adjust the acceleration settings and are done with that.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2004-02-02 20:23 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-01 10:06 2.6 input drivers FAQ Vojtech Pavlik
2004-02-01 13:15 ` Andries Brouwer
2004-02-01 13:50   ` Vojtech Pavlik
2004-02-01 15:14     ` Andries Brouwer
2004-02-02  9:35       ` Vojtech Pavlik
2004-02-02  9:43       ` Vojtech Pavlik
2004-02-01 13:51   ` Marcel J.E. Mol
2004-02-01 15:18     ` Andries Brouwer
2004-02-01 15:25 ` Andreas Jellinghaus
2004-02-01 15:56   ` Peter Osterlund
2004-02-01 16:58     ` Andreas Jellinghaus
2004-02-01 21:54   ` Vojtech Pavlik
2004-02-01 16:31 ` Joshua Kwan
2004-02-01 18:23   ` Gene Heskett
2004-02-02 16:45     ` Valdis.Kletnieks
2004-02-02  5:27   ` Valdis.Kletnieks
2004-02-02  9:23     ` Vojtech Pavlik
2004-02-02 18:12       ` Valdis.Kletnieks
2004-02-02 20:18         ` Vojtech Pavlik [this message]
2004-02-02 20:24           ` Joshua Kwan
2004-02-02 21:16             ` Vojtech Pavlik
2004-02-02 20:28           ` Valdis.Kletnieks
2004-02-02 21:19             ` Vojtech Pavlik
2004-02-02  9:24   ` Vojtech Pavlik
2004-02-02  9:29     ` Joshua Kwan
2004-02-01 21:54 ` 2.6 input drivers FAQ (ir-kbd-gpio.ko) Jose Luis Domingo Lopez
2004-02-02 10:27   ` Gerd Knorr
2004-02-16 22:42   ` Pavel Machek
2004-02-16 23:36     ` Arkadiusz Miskiewicz
2004-02-17  9:33     ` Gerd Knorr
2004-02-02 17:50 ` 2.6 input drivers FAQ Jesse Barnes
  -- strict thread matches above, loose matches on Subject: below --
2004-02-02 11:34 Andries.Brouwer
2004-02-02 12:25 ` Vojtech Pavlik
2004-02-02 12:44 Andries.Brouwer
2004-02-02 12:56 ` Vojtech Pavlik

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=20040202201813.GA272@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@osdl.org \
    --cc=joshk@triplehelix.org \
    --cc=linux-kernel@vger.kernel.org \
    /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