Carol, This is indeed a common problem with jaws. Text Out Delay would
have been my first choice, but 500 is pretty large and has to be
aggravating to work with. The only other timers you can play with are
those in the config manager under Cursor Options. These, especially
Caret Detect Timeout can have an effect on this. Keep both as small as
will do the job to prevent unnecessary sluggishness.
There are two other solutions I know about. One is to use the jaws
cursor rather than the PC cursor. I use an editor called TextPad,
similar to CodeWrite, and it had that problem on slower machines. I
wrote a small set of scripts that detected the jaws cursor hitting the
bottom of the window and did a page down routing the jaws cursor back to
the top. It did likewise on the top side. So, you can use the jaws
cursor like the PC cursor without having to deal with paging. It also
automatically routes the pc cursor to the jaws cursor after the jaws
cursor moves and during speech, so your insertion point is still where
you are reading and the sluggishness is less apparent. I think these
scripts would work as well for codeWrite. If you want, let me know and
I'll bundle them up and send them along.
The next, and perhaps better solution, is to get a faster machine. I
suspect that the fastest compatible video card available would help
accelerate the screen redraw time. Also, using lower resolution might
help this somewhat because less data would have to be redrawn for each
screen update.
Jim Snowbarger
-
Visit the jfw ml web page: http://jfw.cjb.net
