public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Juergen Kreileder <jk@blackdown.de>
To: Esben Stien <b0ef@esben-stien.name>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Logitech MX1000 Horizontal Scrolling
Date: Tue, 05 Apr 2005 20:47:16 +0200	[thread overview]
Message-ID: <87r7hp83ij.fsf@blackdown.de> (raw)
In-Reply-To: 87br8ttgpw.fsf@quasar.esben-stien.name

Esben Stien <b0ef@esben-stien.name> writes:

> Esben Stien <b0ef@esben-stien.name> writes:
>
>> can't find a single problem with the device.
>
> I should mention a couple of things after some testing: There are
> some inconsistencies with regard to cruise control.
>
> When I press TOP CLICK BACKWARD/TOP CLICK FORWARD to cruise control
> down/up, it waits about 100ms

The pause is actually generated by the device, probably to make single
step scrolling easier.

> before it starts cruising. This means that pressing a single click
> does not move me anywhere. I have to hold the key down and wait
> until it starts cruising.

That's a problem with xbindkeys. Without xbindkeys, the X events are
(p = press, r = release)

        p 11/12, p 4/5, r 4/5, ( <pause>, ( p 4/5, r 4/5 )* )?, r 11/12

As the 11/12 events are a bit annoying (Mozilla, but not Firefox,
interprets them as a left click), I use xbindkeys to bind them to
nothing.  But xbindkeys seems to have problems with the press 11/12
and release 11/12 events being interrupted by 4/5 events, it eats
everything before the pause =>

        ( <pause>, ( p 4/5, r 4/5 )* )?, r 11/12

> When I press HORIZONTAL LEFT/HORIZONTAL RIGHT to cruise control
> left/right, it starts immediately going one step in the direction,
> then waits about 100ms before it starts cruising left/right
> again. This means that a single click takes me one click in the
> horizontal direction.

For horizontal scrolling I see:

p 6/7, r 6/7, ( <pause>, ( p 6/7, r 6/7 )* )?

That's OK with me.  If vertical scrolling would work the same way
(ie. without the additional 11/12 events), I'd be happy.

Anyhow, this looks a problem with X not the kernel.  evtest shows that
the device reports similar event sequences for tilting the wheel and
the cruise control buttons.

E.g. scrolling left by tilting the wheel:

,----
| Event: time 1112723029.967722, type 1 (Key), code 280 (?), value 1
| Event: time 1112723029.967729, type 0 (Reset), code 0 (Reset), value 0
| Event: time 1112723029.983709, type 2 (Relative), code 6 (HWheel), value -1
| Event: time 1112723029.983715, type 0 (Reset), code 0 (Reset), value 0
| Event: time 1112723030.359712, type 2 (Relative), code 6 (HWheel), value -1
| Event: time 1112723030.359719, type 0 (Reset), code 0 (Reset), value 0
| Event: time 1112723030.463706, type 2 (Relative), code 6 (HWheel), value -1
| Event: time 1112723030.463715, type 0 (Reset), code 0 (Reset), value 0
| Event: time 1112723030.551708, type 1 (Key), code 280 (?), value 0
| Event: time 1112723030.551712, type 0 (Reset), code 0 (Reset), value 0
`----

and scrolling down with the cruise controll button:

,----
| Event: time 1112723159.628081, type 1 (Key), code 279 (?), value 1
| Event: time 1112723159.628090, type 0 (Reset), code 0 (Reset), value 0
| Event: time 1112723159.644084, type 2 (Relative), code 8 (Wheel), value -1
| Event: time 1112723159.644091, type 0 (Reset), code 0 (Reset), value 0
| Event: time 1112723160.020068, type 2 (Relative), code 8 (Wheel), value -1
| Event: time 1112723160.020075, type 0 (Reset), code 0 (Reset), value 0
| Event: time 1112723160.124067, type 2 (Relative), code 8 (Wheel), value -1
| Event: time 1112723160.124075, type 0 (Reset), code 0 (Reset), value 0
| Event: time 1112723160.212060, type 1 (Key), code 279 (?), value 0
`----

Note the 280 and 279 events at the start and end.


        Juergen

-- 
Juergen Kreileder, Blackdown Java-Linux Team
http://blog.blackdown.de/

  reply	other threads:[~2005-04-05 19:36 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05 15:22 Logitech MX1000 Horizontal Scrolling Esben Stien
2005-02-03 14:42 ` Esben Stien
2005-02-04 19:54   ` Vojtech Pavlik
2005-02-11  7:11     ` Jeremy Nickurak
2005-02-15  2:45       ` Esben Stien
2005-02-15  4:14         ` Jeremy Nickurak
2005-02-15 20:01           ` Esben Stien
2005-02-16  7:10             ` Jeremy Nickurak
2005-03-05 12:56               ` Esben Stien
2005-02-15  2:40     ` Esben Stien
2005-03-05 12:52       ` Esben Stien
2005-03-05 21:09         ` Jeremy Nickurak
2005-03-07 11:48           ` Esben Stien
2005-03-07 18:31             ` Esben Stien
2005-03-08 20:52               ` Vojtech Pavlik
2005-03-08 23:01                 ` Jeremy Nickurak
2005-03-09 11:33                 ` Esben Stien
2005-03-26  1:54                 ` Esben Stien
2005-03-29  8:07                 ` Jeremy Nickurak
2005-04-02 23:44                   ` Esben Stien
2005-04-03 16:01                     ` Juergen Kreileder
2005-04-03 23:41                       ` Jeremy Nickurak
2005-04-05  3:14                         ` Esben Stien
2005-04-05  3:12                       ` Esben Stien
2005-04-05  3:48                         ` David A. Desrosiers
2005-04-05 14:58                           ` Esben Stien
2005-04-05 18:52                             ` Juergen Kreileder
2005-04-05 14:56                         ` Esben Stien
2005-04-05 18:47                           ` Juergen Kreileder [this message]
2005-04-05 22:32                           ` Jeremy Nickurak
2005-04-03 20:23                   ` Peter Osterlund
  -- strict thread matches above, loose matches on Subject: below --
2005-01-07 16:56 Aaron Gyes
     [not found] <3jlKa-2o0-29@gated-at.bofh.it>
     [not found] ` <3tQt7-cV-21@gated-at.bofh.it>
     [not found]   ` <3uhWj-6Tp-27@gated-at.bofh.it>
     [not found]     ` <3wDJ2-1jb-29@gated-at.bofh.it>
2005-03-05  7:16       ` Jeremy Nickurak
2005-03-06  6:01 Aaron Gyes
2005-03-06 20:32 ` Jeremy Nickurak

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=87r7hp83ij.fsf@blackdown.de \
    --to=jk@blackdown.de \
    --cc=b0ef@esben-stien.name \
    --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