--- In [email protected], "entropyreduction" <alancampbelllists+ya...@...> wrote: > > --- In [email protected], "Sheri" <sherip99@> wrote: > > > > FWIW, below is what I get on XP for Word Menu bar and its 13 children. > > Showing only self (child 0) and child 1 because all of the other children > > look exactly the same as child 1. Below that are self (child 0) and child 1 > > of wordpad OBJID_MENU's six children. At the bottom is the script function > > that produced the output. All are property-gets except one function > > (functions do not work period and property gets are very spotty, and no > > facility to translate the role or state). > > > Get_Accessible_Object of WinWord OBJID_MENU: c_3000 > > ================ > > > Children of Main WinWord menu C_3000 > > ......<snip>...... > > > child 1 > > > ---------------- > > Name: // com_type: com_status: ERROR: com.method: Invoke failed (sys > > code 80020009: "Exception occurred.") > > hao.accName could return an exception if the UI item in question had no name. > Maybe. Nameless UI elements are quite common, but what happens when accName > hits one, I dunno. Can;t find docs on that. > > What does Accessibility Explorer give as names for children that cause > exceptions?
Assume you mean AccExplorer 2.0. For Word, it shows the 13 names starting with "File". For WordPad, it shows the 6 names starting with "File". The childcount shown for Word is 13 and for Wordpad it is 6. > > accChild(i) will always return an exception if the child is not a full > IAccessible object, i.e. if it's not associated with an IDispatch. > > http://msdn.microsoft.com/en-us/library/dd318475%28VS.85%29.aspx The page you referenced is for the function, get_accname, not the property h.accname used in the referenced script. None of the functions currently work. I read somewhere that you cannot rely on com macros for determine the success of accessible functions. <http://msdn.microsoft.com/en-us/library/dd318012%28VS.85%29.aspx> Perhaps the plugin should have its own versio of each functions? I think if the MSAA interface were being used correctly, the interface functions would work and the complexity of the fact that some children are simple elements and some objects are would be handled. > > > State: 1073741824 // com_type: com_status: OK > > Default Action: // com_type: com_status: ERROR: com.method: Invoke failed > > (sys code 80020009: "Exception occurred.") > > Quite common for an object not to have a default action. If a child doesn't have a property (such as default action) the function that gets the property (but for, us no interface functions currently work) is supposed to return a non-fatal "not implemented" result. Regards, Sheri
