[jawsscripts] Re: functions SetVerbosityLevel and SetScreenEcho
- From: <marquats@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- To: <jawsscripts@xxxxxxxxxxxxx>
- Date: Mon, 19 May 2008 14:34:20 +0200 (CEST)
The app is self-written, it is not released yet.
There are no frames defined.
I removed the screenStabilizedEvent function.
I turned off all kind of speech output in the configuration manager, but
it had no effect on the multiple speech output.
I also overwrote the NewTextEvent in the Default.jss with a version that
does nothing except saying "default" to check when it is called. But it
also had no effect on the multiple speech output.
I observe the following behavior:
if new text is written on the label(s) by the app, the text is spoken by
Jaws, and *after this*, my app-specific version of NewTextEvent is called.
This is done for every line of text on the *first label*. For text on the
other labels, NewTextEvent is also called, but the text is not spoken
before this call.
The default NewTextEvent is not called at all, when my app has the focus.
I don't know how to understand this. Can anybody please explain why Jaws
behaves like this, or tell me how to avoid the multiple speech output?
> Thomas, u weren't at all specific about the app name so I cannot
> download it & have a look. & it's now getting hard to help w/o
> that information. [...]
>
> NewTextEvent may be called automatically or not, depending
> on many factors, some of which are whether the text is
> highlighted or whether the text is in a frame which is to be
> echoed when it changes or when the screen echo is set to all ...
>
> U could put a different saystring in both the default
> NewTextEvent & your own newTextEvent function to see when both
> are being called. But your screenStabilizedEvent function is
> speaking & it sure shouldn't.
__________
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts
Other related posts: