From: YAMANASHI Takeshi <uncover@beat.cc.titech.ac.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rio /dev/mouse
Date: Thu, 7 Mar 2002 09:48:47 +0900 [thread overview]
Message-ID: <200203070104.g2714g0295248@mail-o.cc.titech.ac.jp> (raw)
Thank you for your enlightenment, rob.
> Long ago, various pieces of the system cleared out the top bits but it
> looks to me like all that code is gone.
High bits of "m.buttons" is cleared in libdraw/mouse.c.
I changed the line
m.buttons &= 7;
to
m.buttons &= 127;
And of course, I have changed rio/rio.c so that rio is now
interpreting rolling wheel as either Kup or Kdown pressed.
--
Sincerely,
YAMANASHI Takeshi
next reply other threads:[~2002-03-07 0:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-07 0:48 YAMANASHI Takeshi [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-08 0:08 YAMANASHI Takeshi
2002-03-07 8:57 Fco.J.Ballesteros
2002-03-07 1:21 Russ Cox
2002-03-07 11:58 ` Boyd Roberts
2002-03-07 1:15 YAMANASHI Takeshi
2002-02-25 18:20 rob pike
2002-02-22 5:35 YAMANASHI Takeshi
2002-02-25 11:48 ` Boyd Roberts
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=200203070104.g2714g0295248@mail-o.cc.titech.ac.jp \
--to=uncover@beat.cc.titech.ac.jp \
--cc=9fans@cse.psu.edu \
/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).