Hi Tom,
This is what I used for smoking out what Word 2007 was using in the
Immediate Mode:
dim i, w, ww: i=0: Set w = ActiveWindow.overlap.children: for each ww in w:
print i & ") " & ww.name: i=I+1: next
0) Default IME
1) MsoDockTop
2) MsoWorkPane
3) MsoWorkPane
4) MsoWorkPane
5) MsoDockLeft
6) _WwF
7) MsoDockRight
8) MsoDockBottom
9) Page number in document. Click
10) MSCTFIME UI
11) Ribbon
12) Collect and Paste 2.0
13) Document1
14) Status Bar
15) Ribbon
16) ScrollBar
17) Microsoft Word Document
18) _WwC
19) MSO Generic Control Container
20) Vertical
21) MSO Generic Control Container
22) Status Bar
23) NUIPane
24) NetUIHWND
25) NUIPane
26) NetUIHWND
27) NetUIHWND
28) NetUICtrlNotifySink
29) NetUICtrlNotifySink
30) NetUICtrlNotifySink
Sent: Monday, August 15, 2011 7:42 PM
Subject: Re: Reading Status Bar in Notepad and Word 2007
Hey Bruce,
Sorry. I should have said I knew it wouldn't work in Word instead of
just giving the example of Notepad. It would be too much to expect
Microsoft to use their own standards. But that's a given.
And just to clarify, wtStatus is not a window name. It's an enumeration
defined within the Window-Eyes object model. In the app developers guide
you'll find it under enumerations, WindowType. All the standard window
types are defined this way; wtDialog, wtButton, wtCheckbox, wtEdit, etc.
But they only apply to standard controls. So I just usually use this
method first via the immediate mode app because it's quick and easy. If
it fails, then I go on the hunt for the non-standard controls and how to
reliably pick them out of the crowd.
Hth,
Tom
