Hello all. I do not think that Jim is really asking how to develop further functionality here. I had a similar issue a while back. It should be noted that my issue was with an application that used MSAA and IE window throughout the scripts and that the issue was with Jaws 12.0. The way I resolved this was to insure that all signs of Jaws specific folders were manually removed. The user settings were also deleted. This is after uninstalling all versions of Jaws and shared components. Additionally I reinstalled the version recompiled the script file in question within TextPad using SCompile. I also seem to remember setting an MSAA flag within my JCF file. The msaa mode can be checked in script utility mode.I finally got this working again after realizing that Th jaws installer does what seems like more of a complete installation when all remnants are removed first. The other question to ask is how are other programs doing when using MSAA? I hope this helps, Jon. Jon Squally Adaptive Computer Solutions LLC Bridging the Gap to Software Accessibility Jaws certified 92% 6/2011 Web site: <http://www.jonsqually.com> Phone: 503.752.2291 Fax: 503.536.6795 Email: support@xxxxxxxxxxxxxx On May 3, 2013, at 9:28 PM, John Martyn <johnrobertmartyn@xxxxxxxxx> wrote: > Did you try GetObjectName? > Joh > > -----Original Message----- > From: jawsscripts-bounce@xxxxxxxxxxxxx > [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Jim Snowbarger > Sent: Thursday, May 02, 2013 7:31 PM > To: jawsscripts@xxxxxxxxxxxxx > Subject: [jawsscripts] MSAA Object Tracking > > This one has me stumped. I wonder if you guys have any ideas. > A client has approached me with a problem application, one of the lovely > Izotope audio applications. It's another one of those apps where the jaws > cursor sees only the window title bar, and nothing else. > The company did some work to make it accessible through MSAA. As a result > of that, Jaws is generally tracking the control with focus as you tab > around. But, the implementation seems a little strange. If you poke around > with the jaws cursor, and just happen to find your way to the control with > focus, you can do getObjectAtPoint, and get the object. But, it has no > parent, no children, and no peers. It is just out in space all by itself. > Jaws can speak the object if you call > SayObjectTypeAndText(). > > > > The problem started to develop when he upgraded to jaws 13, on windows 7 64 > bit, in that some controls were not spoken, while most still were. But, > when he bumped up to jaws 14, all object tracking ceased. He can no longer > hear control names, and > > SayObjectTypeAndText() just says the name of the main window, no matter > where he thinks he is focused. NVDA is able to track the object just fine. > But, jaws has lost track. > > > > He removed jaws 14 and shared components. Even removed jaws 13 and shared, > though presumably there weren't any. So, he thinks he is clean. But > installing jaws 13 by itself, did not recover to previous jaws 13 behavior, > but now exhibits the jaws 14 behavior of not speaking the control in focus. > > > > The weird thing is that jaws 14 tracks the object just fine on my system, > though I have not installed the latest patch, after reading some of the > comments made here. I think he had done so. > > > > Actually, I thought shared components was mostly video intercept logic, and > would have nothing to do with MSAA. > > So, I'm at a loss to help him figure out how to get that working again. > Thus, I come to you. > > Anybody have any suggestions? > > > > Thanks very much. > > > > > > > > __________� > > View the list's information and change your settings at > //www.freelists.org/list/jawsscripts > > __________� > > View the list's information and change your settings at > //www.freelists.org/list/jawsscripts > __________� View the list's information and change your settings at //www.freelists.org/list/jawsscripts