Hi Scriptors: After using WE for some time now with MS Windows 8.1 I have noticed a pattern to some problems. In my in-house Microsoft Visual Studio Developed project WE has trouble holding or finding focus on a Master Detail form with a MenuBar. When I open the menu bar and right arrow WE might read File View File View File View Edit File View file view edit sorts etc... It reads the first couple of menus like the other ones are not there for a few times then might pick up another menu and so on until they are all read but sometimes goes back to the first 2 menus only if I keep arrowing around the Menu Bar, sometimes it works pretty much correctly if I go slow. When I try to down arrow through the Menu Items in one of the menus we may start reading the first few menu items then lock up until I tab or alt tab to change focus to another control and back again. Then it is a struggle to get back into the menu and find a given menu item as described above. Sometimes reading through the ListBox using the arrow keys WE just locks up. Sometimes I might hear the word graphic spoken before it locks up, most times not. Note that sometimes WE works fine but lately it is getting worse and worse. Always When I LogOn to my computer after letting it go into sleep mode WE stutters on the Password like Sta star sta star sta star sta star etc as I type each letter. Sounds like it is trying to read then ReRead the word star cutting off speech in the middle of trying to speek the word twice. Also, after logging on this way my Outlook messages wont read and the last time even Internet Explorer wouldnt read, just ping ping trying to read using the arrow keys in both cases - web problem for WE? Sometimes I hear things spoken that are not in a focused object I am trying to either alt-tab to or otherwise navigate to. Now, all this speaks of WE trying to read more than it should, perhaps reading the entire dom for each keypress or some "hidden" object(s) that are causing WE focus and, or, reading problems? I dont know but this seems to be hinting at some type of problem related to WE trying to find the correct item to hold focus and thus speak. None of these problems are exhibited by JAWS - I have tested them out with the alternate reader to ensure it was not a Microsoft problem. Note that my past experience, postings, on Visual Studio problems fall into this focus problem category as well and that the Visual Studio problems are also not present in JAWS or, for that matter, in a couple of other screen readers I usually have to fall back on. So, these problems may be a result of trying to read the entire dom or WE getting lost in the middle of trying to position itself and allowing focus to get mixed up during this process somehow like trying to handle some hidden object(s) or something else that impacts focus temporarily and, sometimes, causing unresolvable focus problems? While this all is indeed problematic the reason for this posting is to help identify, perhaps, the source(s) of the many problems WindowEyes is having lately so dont take it personally guys but see if you can add to the analysis. Perhaps the WE Staff will have a light bulb moment if they see a pattern and recognize something from their deep knowledge of the WE code base. I posted to the talk list to see if anyone has noticed these types of problems as well but not so much detail just in case they can add something relevant. Note that if I go really slow sometimes some of these problems don't crop up so often but sometimes they still do. 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/scripting-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com
