Hi Rick, My CappEnhance is pretty straightforward in its processing of individual characters, and I've noticed a change in how Window-Eyes processes characters using the screen voice, and you have brought this to light. Frankly, I can't do much without knowing what has changed in the Window-Eyes code with version 9.3. It does occur to me that perhaps Visual Studio is using custom controls to display their text, and perhaps they cause normall text-handling routines to be bypassed or modified. Sorry, but I can't think of what to do.
Cheers, Rod -----Original Message----- From: Talk [mailto:[email protected]] On Behalf Of Rick Thomas via Talk Sent: December 30, 2015 8:20 AM To: 'Window-Eyes Discussion List' <[email protected]> Subject: AISquared et All: OfficeEnhance Blew Up Hi: I have been getting some lightly unusual results off and on like hitting top of form in a list and not hearing the first entry read unless using the arrow keys. I also have been having problems in Visual Studio with CapEnhance not reading caps in a diferent pitch, tone nor volume. When I set WE to use pitch for caps in the WE Control Panel it reads the entire word in the higher pitch when reading a line. Now, typing a message to Rod I got a message that there was an error and asked if I want to send it to gw which I don't think I did by mistake after trying to figure out how to read the entire thing including the title bar to get which app blew up. It was the OfficeEnhance.vbs app at line 563, column 1 and was listed as an "Undefined Error" the number was 0x80004005 I think. I think this error happened a couple of weeks ago and someone else also had it. I found that I could not click the Edit button nor the help buttons on the error dialog, they were disabled. So I just continued and ReBooted the computer. Things seem to be working ok for now but I am hesitant to go into Visual Studio just to test in case there are problems beyond the CapEnhance situation and, in fact, in the WindowEyes scriptpts themselves that may be impacting Office related objects used by Visual Studio and thus perhaps Rods Script by not executing it or something. I do note here that Visual Studio uses certain Office DLLs to run some features, don't know how all that works, but I also note that WindowEyes required me, under Windows 8.1 to install some downlevel, quite old, versions of Office DLLs which I have not done for Windows10 since all files were suppose to have been left in place. OK, first what is causing, caused, the error in the OfficeEnhance script? What is on the line that blew up? What does it and the lines around it do since I cant seem to have edited the script myself to look for the problem. This appears to have been the second time, at least that I was notifyed about, this has happened and has happened on someone elses machine so what was going on in the WindowEyes VB Script at and around that line number so I can see how it may apply to my system and my programs. Could those very old Office DLLs I had to load be impacting the new Visual Studio 2013? 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
