Eric.Bohlman@p1.f778.n115.z1.fidonet.org (Eric Bohlman) (10/13/90)
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.orgGary.Petraccaro@f90.n129.z1.fidonet.org (Gary Petraccaro) (10/17/90)
Index Number: 11157
[This is from the Blink Talk Conference]
Eric,
The mouse may prove a real problem. If we move the cursor now, we
move by line, character, word, sentence, but we usually have an idea what
we've used as a unit. How we gonna do that with a mouse? Could you put in
a move by character with character reading if moving slow and if moving
fast put in a cursor coordinates readout with the whole line read next?
Don't know what that would be like in practice, but that's about the best I
can come up with on short notice.
--
Uucp: ..!{decvax,oliveb}!bunker!hcap!hnews!129!90!Gary.Petraccaro
Internet: Gary.Petraccaro@f90.n129.z1.fidonet.orgEric.Bohlman@p1.f778.n115.z1.fidonet.org (Eric Bohlman) (10/17/90)
Index Number: 11170
[This is from the Blink Talk Conference]
I'd probably make the "landing unit" definable (character, word, line, etc.)
like I make vertical cursor movement definable. One of the characteristics of
a mouse or trackball is that it doesn't usually move the mouse cursor in a
straight line; it may bounce a bit. That's one of the reasons I was thinking
of waiting until the movement stopped. Announcing the row/column position
sounds like a good idea; I'd make it a selectable option.
Another consideration is verbalizing the kinds of objects used by programs
that support meese. Scroll bars would be one example. Dialog boxes with
"checkboxes" and "radio buttons" are another, though these can also be found
in non-mouse-specific programs.
--
Uucp: ..!{decvax,oliveb}!bunker!hcap!hnews!115!778.1!Eric.Bohlman
Internet: Eric.Bohlman@p1.f778.n115.z1.fidonet.org