Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!yale!bunker!hcap!hnews!129!26!Jack.O'keeffe
From: Jack.O'keeffe@f26.n129.z1.fidonet.org (Jack O'keeffe)
Newsgroups: misc.handicap
Subject: SEEBEEP
Message-ID: <10127@bunker.UUCP>
Date: 13 Feb 90 05:19:09 GMT
Sender: wtm@bunker.UUCP
Reply-To: Jack.O'keeffe@f26.n129.z1.fidonet.org
Distribution: misc
Organization: FidoNet node 1:129/26 - SoundingBoard, Pittsburgh PA
Lines: 38
Approved: wtm@bunker.UUCP

Index Number: 6718

[This is from the Silent Talk Conference]

Hi, Wayne.  Stu sent SeeBeep to me, and I have to say that it is
of very limited value here.  Possibly if I was a more accomplished
typist, and could give the screen undivided attention, it would be
more useful.  As it is, fully half my attention is on trying to hit
the correct keys, and I miss seeing the little "BEEP" on screen.

Since it is a TSR, and does intercept the beep to the speaker, it
would be useful if it could optionally supress the speaker as well.
That would help preserve domestic tranquility for those of us who
are addicted to late night BBSing, and live with hearing partners
who prefer to sleep.

I use the Silver Xpress reader, which has "exploding windows" for
menus and messages.  You should see what SeeBeep does to those.
The exploding window is made by rapidly alternating calls to the
screen and to the speaker.  Since SeeBeep intercepts the speaker
calls it has the effect of making the window "explode" in slow
motion.

I am using a beta (or is it a gamma) version of Silver Xpress, and
it has an interesting new feature that solved my personal "beep"
problem.  With it you can configure the audio frequency of the beeps.
Since I have a corner of residual low frequency hearing in my "good"
ear, I configured the reader to beep at 400 hz. and I can hear it.

Thanks for bringing SeeBeep to our attention.

Jack.

... HI-HoH Silver, Awayyyyy!

--
Uucp: ..!{decvax,oliveb}!bunker!hcap!hnews!129!26!Jack.O'keeffe
Internet: Jack.O'keeffe@f26.n129.z1.fidonet.org