Path: utzoo!attcan!uunet!cs.utexas.edu!yale!bunker!hcap!hnews!115!778.1!Eric.Bohlman
From: Eric.Bohlman@p1.f778.n115.z1.fidonet.org (Eric Bohlman)
Newsgroups: misc.handicap
Subject: noisy rodents
Message-ID: <14957@bunker.UUCP>
Date: 12 Oct 90 19:44:18 GMT
Sender: wtm@bunker.UUCP
Reply-To: Eric.Bohlman@p1.f778.n115.z1.fidonet.org
Distribution: misc
Organization: FidoNet node 1:115/778.1 - COPH-2 (BGMS), Chicago IL
Lines: 23
Approved: wtm@bunker.UUCP

Index Number: 11096

[This is from the Blink Talk Conference]

I'm considering adding mouse support to Tinytalk.  However, I have
only a vague idea of how it should behave.  One thought is that it
should say nothing while the mouse cursor is moving (too much
output, mostly interrupting itself) and then read whatever the
mouse cursor is sitting on once the cursor has been stationary for
a moment.  The question is what it should read: lines, characters,
lightbars, what have you (note that all this assumes a text-mode
screen display.  I hope to tackle Windows eventually, but don't
hold your breath).  How would you want mouse tracking to behave?
One thing I DON'T want to do is make use of the mouse buttons,
since that would interfere with applications that were using them.

One random thought that just popped up is that if the mouse cursor
lands in a bordered box, it should speak only the portion of the
line within the box.

--
Uucp: ..!{decvax,oliveb}!bunker!hcap!hnews!115!778.1!Eric.Bohlman
Internet: Eric.Bohlman@p1.f778.n115.z1.fidonet.org