Hi Chip: The setfocus to the File menu of the MenuBar AutomationElement worked
fine.
I believe there is something called virtual focus set on the last child
AutomationElement that has focus whenever focus leaves SolutionExplorer.
>From what I read that tells the OS to go back to that AutomationElement if
>there is no focus for the window or SolutionExplorer again is set up to be
>visible on screen.
>From my readings so far the methods of handling keyboard input are to use
>WM_Whatever and, or, monitor window messages.
The complexity comes in when I consider the fact that the Target App will be
running in it's own process (apartment too) and my script and perhaps WE in
other apartments.
I am not sure if the WM_Whatever written in my script will monitor keyboard
input outside my apartment, process, still not totally clear on that yet but it
could pose a problem.
Things get complicated quickly when looking at WM_Whatever and cross-Process
handling.
Then there are the Message queus which may, or not, offer a solution.
Does anyone have a suggested methodology so I can narrow a solution down to a
single technical to start reading and testing?
Anyway the UIA stuff seems to work ok so far. It is the non-uia stuff that is
giving me more gray hair, darker gray since I think it is all gray
already.Thanks
Rick USA
