Most WE events don't return values, but the OnFieldData/Name/Summary, and their OnChildField* parallels, return strings or vbNull. My understanding is that Window-Eyes speaks what these events return.
So say you have three applications loaded, all of which include a ConnectEvent for OnChildFieldName from the Desktop window. They can (and absolutely should of course) filter their responses by checking for process Ids, but they still each have to return something - should be vbNull. So the question: How does Window-Eyes decide who to listen to? Does it just speak the first non-null result it gets back, or does it speak all non-null results from the different event functions? I assume if it speaks any one of them, it would not go ahead and speak its own default response as well. Btw, I regard this scenario of multiple Desktop window hooks for OnChildField* events as very likely, because it seems the safest way to avoid problems if the top-level window of an application is not constant. This is also very likely in the presence of pop-up dialogs and such. My question is mostly so I can detect any interferance one script might cause to another in this area. -- Doug Lee, Senior Accessibility Programmer SSB BART Group - Accessibility-on-Demand mailto:[email protected] http://www.ssbbartgroup.com "While they were saying among themselves it cannot be done, it was done." --Helen Keller
