From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: [9fans] sound of moving mouse ^_^
Date: Fri, 16 Nov 2001 10:15:26 +0900 [thread overview]
Message-ID: <20011116011439.EE268199EA@mail.cse.psu.edu> (raw)
This is just from curiosity. :-)
My DEC PC leaks small sound to my speaker␣boxes when I move the mouse.
When I do it on an acme window, it sounds in lower pitches than on
a raw rio windows. Yes, the difference is considerablly large. I suppose
this may reflect the rate of something related to detect the mouse event.
If so, that is higher in raw rio than in acme. Is this right? :-)
Kenji
next reply other threads:[~2001-11-16 1:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 1:15 okamoto [this message]
2001-11-16 1:34 ` Skip Tavakkolian
2001-11-16 1:43 okamoto
2001-11-16 2:06 ` andrey
2001-11-16 2:26 ` paurea
2001-11-16 2:35 ` andrey
2001-11-16 2:35 okamoto
2001-11-16 3:01 rob pike
2001-11-16 3:45 ` paurea
2001-11-16 19:51 David Gordon Hogan
2001-11-16 19:54 David Gordon Hogan
2001-11-16 21:32 ` Sam Ducksworth
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=20011116011439.EE268199EA@mail.cse.psu.edu \
--to=okamoto@granite.cias.osakafu-u.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).