public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Nickurak <atrus@rifetech.com>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Esben Stien <b0ef@esben-stien.name>, linux-kernel@vger.kernel.org
Subject: Re: Logitech MX1000 Horizontal Scrolling
Date: Tue, 29 Mar 2005 01:07:26 -0700	[thread overview]
Message-ID: <1112083646.12986.3.camel@localhost> (raw)
In-Reply-To: <20050308205210.GA3986@ucw.cz>

[-- Attachment #1: Type: text/plain, Size: 778 bytes --]

On Tue, 2005-03-08 at 21:52 +0100, Vojtech Pavlik wrote:
> The problem is that the mouse really does reports all the double-button
> stuff and autorepeat, and horizontal wheel together with button press on
> wheel tilt.

Okay, I'm playing with this under 2.6.11.4 some more, and it really
seems out of whack. The vertical cruise control buttons work properly,
with the exception of the extra button press. But the horizontal buttons
are mapping to 6/7 as non-repeat buttons, and adding simulateously the
4/5 events auto-repeated for as long as the button is down. That is to
say, pressing the the horizontal scroll in a 2d scrolling area will
scroll *diagonally* one step, then vertically until the button is
released. 

-- 
Jeremy Nickurak <atrus@rifetech.com>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-03-29  8:30 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 [this message]
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
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=1112083646.12986.3.camel@localhost \
    --to=atrus@rifetech.com \
    --cc=b0ef@esben-stien.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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