Hi Rick, It is my belief that it is not necessarily true that the fast speech is due to the WE cursor voice. Having checked the App Developer's reference manual, there is no separate setting for the rate of the WE cursor; Rather, if it is due to one of the floating cursors as it were, that is, either mouse or WE, then it must be the rate of the mouse voice. As I see it, then, the fast speech is either due to a window which has a fast rate for either screen voice or mouse voice. However, I think it is more likely that the fast speech you are hearing is due to a high rate for the screen voice in a specific window which is being triggered in Visual Studio and Internet explorer. Finding that trouble-maker window is the key, but it's obviously something common to both programs, Visual Studio and Internet Explorer. Actually, perhaps it's simpler to conclude that there is some window in the operating system in general which is being read at the wrong time.
I hope this helps, Rod -----Original Message----- From: Talk [mailto:[email protected]] On Behalf Of Rick Thomas via Talk Sent: Thursday, May 14, 2015 2:57 PM To: 'Window-Eyes Discussion List' Subject: WE Problem Patterns Continued OK Guys: One problem for phantom reading is narrowed some. When I was working in my own project, developed in Visual Studio, and again while in Internet Explorer, there were a couple of phantom things read, or at least they started to read. In my project I have a list box and 2 text boxes on a form. When I tabbed into the list box I heard the first couple of words from inside one of the text boxes read at high speed indicating it was the WE Cursor reading it before the first line in the list box was read. The WE cursor was not turned on or active since the normal mouse cursor was active. After reading the first word and starting the second word we cancelled speech and continued in normal fashon with focus properly placed in the list box. The same thing happened in Internet Explorer only I think something in the supposedly closed Menu Bar were spoken fast, again indicating it was the WE Cursor and not the Mouse cursor nor the Focus of the normal cursor. Yesterday, per Chips suggestion I ensured the Speak Tool Tips was unchecked so this was not causing this problem and it is still turned off as I type this. This well may have caused the phantom word "graphic" to have been spoken as noted the past couple of days. Also when this happens it seems to take WindowEyes longer to get focus set properly and perhaps may muck up WindowEyes timing of other activities behind the scenes. Is there a setting that turns off even trying to read the WE Cursor as part of the WindowEyes behind the scenes processing of forms and pages? This appears to be one problem narrowed enough to ask about and perhaps identify as a bug if there is not a setting to stop this errant behavior. Rick USA _______________________________________________ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/rod_hutton%40h otmail.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com _______________________________________________ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
