From: Jeremy Nickurak <atrus@lkml.spam.rifetech.com>
To: Aaron Gyes <floam@sh.nu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Logitech MX1000 Horizontal Scrolling
Date: Sun, 06 Mar 2005 13:32:20 -0700 [thread overview]
Message-ID: <1110141140.4727.3.camel@localhost> (raw)
In-Reply-To: <1110088883.24801.3.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 584 bytes --]
On sab, 2005-03-05 at 22:01 -0800, Aaron Gyes wrote:
>I worked around the weird two button thing by disabling cruise control.
Unfortunately:
1) This requires third-party software to work
2) This also disables the up/down scrolling cruise control buttons. The
buttons above and below the scroll wheel are supposed to not only be
remapped to buttons 4 and 5, but also have a auto-repeat added when held
down. (The same auto-repeat is also required by the horizontal
scrollers, unless it's to be dictated that user-space software needs to
apply their own repeat mechanism)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-06 20:33 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 6:01 Logitech MX1000 Horizontal Scrolling Aaron Gyes
2005-03-06 20:32 ` Jeremy Nickurak [this message]
[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
-- strict thread matches above, loose matches on Subject: below --
2005-01-07 16:56 Aaron Gyes
2005-01-05 15:22 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
2005-04-05 22:32 ` Jeremy Nickurak
2005-04-03 20:23 ` Peter Osterlund
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=1110141140.4727.3.camel@localhost \
--to=atrus@lkml.spam.rifetech.com \
--cc=floam@sh.nu \
--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