From: Jeremy Nickurak <atrus@lkml.spam.rifetech.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Logitech MX1000 Horizontal Scrolling
Date: Sun, 03 Apr 2005 17:41:00 -0600 [thread overview]
Message-ID: <1112571660.23238.5.camel@localhost> (raw)
In-Reply-To: <87u0mn3l4e.fsf@blackdown.de>
[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]
On dim, 2005-04-03 at 18:01 +0200, Juergen Kreileder wrote:
> Esben Stien <b0ef@esben-stien.name> writes:
>
> > Jeremy Nickurak <atrus@rifetech.com> writes:
> >
> >> I'm playing with this under 2.6.11.4
> >
> > I got 2.6.12-rc1
> >
> >> The vertical cruise control buttons work properly, with the
> >> exception of the extra button press.
> >
> > Yup, nice, I see the same
>
> Same here.
>
> >> 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.
> >
> > Yup, seeing exactly the same here.
>
> Horizontal scrolling works fine for me. I just get repeated 6/7
> events, nothing else.
>
> I'm using the configuration described at:
> http://blog.blackdown.de/2005/04/03/logitech-mx1000-configuration/
Well that's a big step up. My horizontal scrolling is now working
perfectly. I had never in my life seen a ZAxisMapping line with 4
buttons, but it seems to do the trick, and it's even worked its way into
the mouse man page since the last time I remember seeing it. (Running
current Xorg here, can't speak for XFree86 users)
Now it's just the vertical scroller issue.
-
Jeremy Nickurak
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-03 23:41 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 [this message]
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=1112571660.23238.5.camel@localhost \
--to=atrus@lkml.spam.rifetech.com \
--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