- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Susan Fulton: "Re: Vocabulary size"
- Previous message: dselesky@@lhs.com: "natural language commands"
- Maybe in reply to: Aaron Green: "Making MouseGrid more usable"
- Next in thread: Rose: "Re: Making MouseGrid more usable"
Rose
Aaron Green wrote:
>
> 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
>
> Anyway, here is a re-send of one of my messages that did not get
> through:
>
> (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& = Val( _arg2 ) * 3" to "nDistance& = 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.
>
> 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.
>
> Hope this helps some people.
>
>
>
>
- Next message: Susan Fulton: "Re: Vocabulary size"
- Previous message: dselesky@@lhs.com: "natural language commands"
- Maybe in reply to: Aaron Green: "Making MouseGrid more usable"
- Next in thread: Rose: "Re: Making MouseGrid more usable"
 |  |