Voice-Users: Making MouseGrid more usable

------=_NextPart_000_003B_01BDA9C6.942AE5E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I figured out why I wasn't getting my messages through: you can't send =
messages to the "from" email address... you have to use the "reply to" =
address

(One thing: since this is long, and it takes awhile to scroll through =
the digests sometime, if you reply to this on the Digest, please delete =
the bulk of this message before sending! You can press or put in a macro =
{Ctrl+Shift+End}Del )

Clicking is very hard on the wrist, and MouseGrid is more usable than I =
thought! I have two things to make MouseGrid easier:

1. Here is the basic thing: call out numbers before the grid appears. =
There is a delay before the grid appears in case you do exactly that. I =
did not use MouseGrid at first because it seemed so slow, but you start =
to get to hang of it, especially if you call out the initial position at =
first, and then, USING THE GRID ON THE SCREEN, see in your head the next =
two or three numbers that represent the "sub-segments" within the =
current segment that will take you to the point you are trying to =
reach... and call them out immediately. Soon, you will be able to call =
out numbers, and then watch the mouse move exactly where you wanted it =
to move!

2. Here is an adjustment you can make if you have the Deluxe edition: =
After you get in the general vicinity, it would be nice to use the =
"mouse move" command, if it were not so limited. I consider it limited =
because you can only move the mouse so far with one command. If you have =
the Deluxe edition, however, you can change things a bit: edit the =
global script "Mouse <Direction> <1To10>" and do the following:

(a) To make the mouse move farther for any given number 1-10, change the =
line "nDistance& =3D Val( _arg2 ) * 3" to "nDistance& =3D Val( _arg2 ) * =
7"... Actually, changing from 3 to 7 is just something that worked well =
on my 800 by 600 screen. You can try different numbers (the greater the =
number, the more the mouse for move for each number, 1-10)

(b) Change the maximum number of "spaces" the mouse can move: to do =
this, when you select to edit the script "Mouse <Direction> <1To10>" and =
click "next," change "<1To10>" to "<2To20>"... The list "<2To20>" is =
already defined; if you want to define a different range, you could do =
so. So with this range, you could call out any number from 2 to 20.

The cool thing: after making changes (a) and (b) this morning, I can use =
the MouseGrid to move to a specific segment of the screen just once, and =
then, if I wish, use "Mouse <Direction>" to traverse the entire segment =
of the screen that I just specified. Before, I would have had to use =
many "move" commands or continue to use MouseGrid in order to select =
appoint within that segment.=20

But I still think using MouseGrid to specify multiple sub-segments-- at =
least BEFORE using "Mouse <Direction>"-- is superior and something you =
can get very used to doing.

------=_NextPart_000_003B_01BDA9C6.942AE5E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I figured out why I wasn't getting my messages through: you can't = send=20 messages to the "from" email address... you have to use the=20 "reply to" address

Anyway, here is a re-send of one of my messages that did not get=20 through:

(One thing: since this is long, = and it takes=20 awhile to scroll through the digests sometime, if you reply to this on = the=20 Digest, please delete the bulk of this message before sending! You can = press or=20 put in a macro {Ctrl+Shift+End}Del )

----------------

Clicking is very hard on the wrist, and MouseGrid is more usable than = I=20 thought! I have two things to make = MouseGrid=20 easier:

1. Here is the basic thing: call out numbers before the grid appears. = There=20 is a delay before the grid appears in case you do exactly that. I did = not use=20 MouseGrid at first because it seemed so slow, but you start to get to = hang of=20 it, especially if you call out the initial position at first, and then, = USING=20 THE GRID ON THE SCREEN, see in your head the next two or three numbers = that=20 represent the "sub-segments" within the current segment that = will take=20 you to the point you are trying to reach... and call them out = immediately. Soon,=20 you will be able to call out numbers, and then watch the mouse move = exactly=20 where you wanted it to move!

2. Here is an adjustment you can make if you have the Deluxe edition: = After=20 you get in the general vicinity, it would be nice to use the "mouse = move" command, if it were not so limited. I consider it limited = because you=20 can only move the mouse so far with one command. If you have the Deluxe = edition,=20 however, you can change things a bit: edit the global script "Mouse = <Direction> <1To10>" and do the following:

(a) To make the mouse move farther for any given number 1-10, change = the line=20 "nDistance& =3D Val( _arg2 ) * 3" to "nDistance& = =3D Val(=20 _arg2 ) * 7"... Actually, changing from 3 to 7 is just something = that=20 worked well on my 800 by 600 screen. You can try different numbers (the = greater=20 the number, the more the mouse for move for each number, 1-10)

(b) Change the maximum number of "spaces" the mouse can = move: to do=20 this, when you select to edit the script "Mouse <Direction>=20 <1To10>" and click "next," change = "<1To10>"=20 to "<2To20>"... The = list=20 "<2To20>" is already defined; if you want to define a = different=20 range, you could do so. So with this range, you could call out any = number from 2=20 to 20.

The cool thing: after making changes (a) and (b) this morning, I can = use the=20 MouseGrid to move to a specific segment of the screen just once, and = then, if I=20 wish, use "Mouse <Direction>" to traverse the entire = segment of=20 the screen that I just specified. Before, I would have had to use many=20 "move" commands or continue to use MouseGrid in order to = select=20 appoint within that segment.

But I still think using MouseGrid to specify multiple sub-segments-- = at least=20 BEFORE using "Mouse <Direction>"-- is superior and = something you=20 can get very used to doing.

Hope this helps some people.