Hi Rick,
I have something for you. This is what you can do to get you started
reading a ribbon. But the object you get focus to also has other values,
such as collection and stuff, so you have to expand this routine to be
inclusive on what you are focused on.
Your app example
'Global variables
'Watch all your events:
Dim myMSAAEvents: Set myMSAAEvents = msaaEventSource
'The event connection that is saved for shut-down disconnect value.
Dim myMSAAConnection: myMSAAConnection = 0
' Now in your hotkey proc you call for your application getting it's window
and saving it's process ID.
myMSAAEvents.Process = oWindow.Process
On Error GoTo 0
' Now handle all MSAA event types you choose based on the name after the
underline.
myMSAAConnection = ConnectObject( myMSAAEvents, "myMSAA_")
Sub myMSAA_OnObjectFocus( oFocus)
' event handler and sort out key up and down on this.
' called when MSAA signals some text is focused.
'So, Rick this will say your labels when hitting alt, tab, or cursor keys.
Speak oFocus.Name
End sub
Sent: Friday, July 15, 2011 6:10 AM
Subject: Re: UI Object Module?
Hi Guys: I am following this. I am confused about if you are talking about
UIA or just UI.
UIA is the new accessibility methodology being used by Microsoft and not
supported in WE Scripting.
UI just stands for User Interface and can be anything from a simple message
box to a full blown Dialog with all kinds of controls on it.
It sounds like he means UIA except that I don't know what he means about
support using the Accessible and numbers to get UI Events. That sounds like
perhaps events related to UI elements like a Dialog rather than UIA.
Then there was the bit about modules and Word and Chip's app using a com
interface. Now I am really guessing at this point if we are talking about
accessing a DOM using UIA or if we are talking about accessing events of
objects like a Dialog which is supported currently in WE.
Some of the words would seem to relate to UIA hooking under a WE Script and
some of them sound like he is just asking how to write a basic script and
get events to the standard xml UI objects built by the GW guys.
As for the Com reference, that one has me really confused unless it relates
somehow to a indirect way of getting at the UIA version of the DOM from
within a WE script.
Anyway, what are we talking about here?
I would like to know so I can follow this thread as I would like to know how
to access the direct UIA dom structures if that is what you guys are trying
to do.
The MSAA reference by Chip makes me think this is the case but the other
stuff makes me think he just wants to learn how to script xml objects, or
perhaps he wants to script MS Framework objects or something else.
All are quite diferent and the com reference really throws me off.
Rick USA
- don't there is no support for UIA that I remember under the
----- Original Message -----
From: "BT" <[email protected]>
To: <[email protected]>
Sent: Thursday, July 14, 2011 10:48 PM
Subject: Re: UI Object Module?
>
> Hi Chip,
>
> Yes, I found the UI page for Microsoft, but not GW's version.
>
> I read that the accessible is the way to go and found the way using
> event register and such to get the events. Which boils down to reading
> numbers and such for each event. Not a pretty way to do things.
>
> When liking through The GW documentation, I could not find anything,
> the
> reason for my comment. At least anything that said A UI. No search found
> anything UI.
>
> So, I did a search on UI objects and came up with 3 results that made
> sense. Now, have not tested them yet, but led me to all the events, and
> numbers, and such to at least find a way to monitor events.
>
> In other words, in Word, which you wrote and I spent a lot of time
> going
> through, there are objects to call everything. When reading and
> downloading
> the stuff I found on 2003 and 2007 I discovered how you came up with your
> way of writing your script. It was easy since there was a Com call you can
> make and lots of object to play with.
>
> Now, UI has only 2 ways to do things, an automation way and and another
> way I have forgotten about at the moment. Not as easy as Wood does things.
> The reason why I mentioned 2003 and 2007, for there is lots of
> documentation
> on it.
>
> So, will read and test what I found and see where I go from there.
> Simple steps to getting use to writing script...A pain to find true
> documentation for.
>
> Bruce
>
> Sent: Thursday, July 14, 2011 8:18 PM
> Subject: RE: UI Object Module?
>
>
> Bruce,
>
> if you mean Office 2003 or 2007, the object model for office 2010 really
> has
> nothing to do with UI automation, and can easily be found online.
> My understanding is that Microsoft (and GW), have provided a bridge to
> MSAA
> objects and events, so that we'll continue to get information in our apps,
> even when we're dealing with an app using UI automation. I understand
> it's
> not perfect, but it is usable until more work can be done.
>
> Chip
>
>
> -----Original Message-----
> From: BT [mailto:[email protected]]
> Sent: Thursday, July 14, 2011 1:04 PM
> To: [email protected]
> Subject: UI Object Module?
>
>
> Hi!
>
> OK, since UI is being used, is there a page, or link to go to to get
> the
> object model for the UI controls?
>
> I have downloaded all the GW Micro has on 2003, and 2007 and now there
> is no place that I can see for any link to the UI object model version of
> the same stuff. Just spent several hours looking.
> But, as usual, there is always something the screen reader misses.
>
> so, Doug or Aaron, can you send me the link that has the same stuff as
> 2003 - 2007 has at Microsoft web sites?
>
> When attempting to look into a ribbon program I ended up writing my own
> version of the same program you wrote on listing all classes or modules
> inside a ribbon, but what next? The Windows10 keeps coming up, but nothing
> under it, but more of the same...
> Bruce
>
>
