From: kvik@a-b.xyz
To: 9front@9front.org
Subject: Re: [9front] nusb/kb mouse handling
Date: Wed, 09 Dec 2020 00:14:50 GMT [thread overview]
Message-ID: <0837C1671575B6BA0BF49EF1E2851C00@hog> (raw)
In-Reply-To: <E1CA79C0E9F4F56FC73FA4440E285B3A@prosimetrum.com>
Quoth umbraticus@prosimetrum.com:
> Nice. So you'd be in favour of b4 starting at 32, skipping over the
> scrollwheel's 8/16. The owner of the "logitech 5 button mouse" could
> follow your lead if he still wants b4 mapped to b2, or we could extend
> the buttonmap functionality described in mouse(3) ...
The way I see this, the driver should report unmapped input events and
let the rest of the input system decide what they mean.
The problem with mapping in mouse(3) is with it applying to all devices,
making it useless for dealing with per-device oddities.
I don't have a big idea on how to handle the general input issue.
Mousetrap works to make my Huge usable but I'm not convinced that it's
the way things oughta be.
The main problem is nothing in Plan 9 knows how to deal with these extra
input events. If I'm remembering correctly we'r even filtering out
anything above 0x10 in mouse(3) or rio.
prev parent reply other threads:[~2020-12-09 0:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 0:59 umbraticus
2020-12-08 8:44 ` umbraticus
2020-12-08 11:37 ` umbraticus
2020-12-08 13:50 ` kvik
2020-12-08 21:18 ` umbraticus
2020-12-09 0:14 ` kvik [this message]
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=0837C1671575B6BA0BF49EF1E2851C00@hog \
--to=kvik@a-b.xyz \
--cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).