--- In [email protected], "Sheri" <sheri...@...> wrote: > > Our access to accessibility should work more like other com interfaces. We > should be able to see functions like get_acchild for an IAccessible in > get_object_description, and the functions should work. Currently only > properties work and then only sometimes. Com exceptions seem to be the norm > at present. But can't even see on get_object_description, and no typeinfo. > Maybe you failed to include oleacc.h.
I don't include oleacc.h. I load accessibility API func entry points dynamically, so plugin doesn;t fall over in absence of relevant dll. > Hopefully useful links: > > <http://blogs.msdn.com/oldnewthing/archive/2004/04/23/118893.aspx> > <http://www.nvda-project.org/browser/devTools/MSAAWalker> > <http://www.autohotkey.com/forum/topic48629.html> > Re BSTRs: > <http://blogs.msdn.com/ericlippert/archive/2003/09/12/52976.aspx> Will read when I get a chance. In the meantime: http://blogs.msdn.com/lixiong/archive/2009/12/05/ui-automation-under-the-hood.aspx "IAccessible is not a standard COM interface. The caller is not required to invoke CoInitialize, but the caller cannot use QueryInterface to continue obtain further interface." Further refs in article. > BTW, the previous com release .70 also crashes trying to retrieve wordpad's > Paste item in XP on that demo script. So no harm done releasing .72 without > fixing that particular issue yet. > The recent revision of the script to try with Word removed the role text > "popup menu". Without that, when used with wordpad, it apparently returns the > first item in the app named "Edit" which (at least on XP) is not the Edit > popup menu handle that owns the simple child named Paste. Word script will not work with wordpad, because the two apps don't have same structure. In particular menu ribbon has different staus in two apps. Use Winspector Spy or Accessibility Explorer to see the diff.
