mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeremy Nickurak <atrus@rifetech.com>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Logitech MX-Series "Cruise Control" buttons
Date: Sun, 06 Feb 2005 12:05:17 -0700	[thread overview]
Message-ID: <20050206190517.GA8046@agaeris.rifetech.com> (raw)

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

I recently posted an update to http://bugme.osdl.org/show_bug.cgi?id=1786 that shows the bug escalating on newer hardware, such that there is no user-accessable workaround.

It seem that where an MX-series mouse's cruise-control buttons are concerned, the mouse (by default) produces two events for each button press: The button itself, as well as a scroll event simulating a keyboard-style press-delay-repeat cycle on the scroll wheel axis/buttons.

Utilities such as logitech_applet (unmaintained afaict) seem to be able to change some settings. For example, on my MX1000 mouse it's able to disable the cruise-control scroll button simulation, which would allow me to use the buttons as ordinary mouse buttons. What I'd love to do is to be able to disable the button's native function and use *only* the cruise-control function, as the mouse was intended.

If such a hardware reconfiguration is not possible, perhaps it would be easier to leave the mouse in the default configuration, but filter one event or the other before it reaches userspace? Or is it more natural to filter out the mouse's scroll-simulation, and do a mapping & key-repeat simulation in userspace somewhere?

Please CC me in replies.

-- 
Jeremy Nickurak -= Email: atrus@lkml.spam.rifetech.com =-
Remember, when you buy major label CD's, you're paying
companies to sue families and independant music. Learn
more now at downhillbattle.org.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2005-02-06 19:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20050206190517.GA8046@agaeris.rifetech.com \
    --to=atrus@rifetech.com \
    --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

all inboxes | Powered by JetHome®