Hi GW Guys:
Does the WE>Key>KeyProcessed methods rely on message broadcasting?
Does it do something like receive a message and then SendMessage or something 
to pass through any Keyboard inputs to the Target Application?
I am not sure how WM still handles Message Processing but UIA does not make use 
of it directly as a Client feature.
A Client has to subscribe to events and no Keyboard Inputs are provided by 
default for the AutomationElement object in UIA as far as I can tell so far.
There is a method to handle Synchronized Operations but the Programmer of a 
Target Application needs to make these events available from the Provider model 
they work with or the events are not available to a Client like WindowEyes or 
me and my WE Script via the Pattern if I read that technical correctly.
My questions are:
1) Does the WE>Key>KeyProcessed methods rely on the Broadcast technicals and 
can that be impacting them so that keystrokes are not passed through to the 
Target Application?
2) Do you think that WM or WMI will still offer a way around UIA not using the 
Broadcast method of message processing?
I am wondering about trapping a Keyboard message using WM or WMI and then 
Sending it out again after handling it in my script.
My concern is is that if WE is doing this already in the Key>KeyProcessed 
methods that there may be some problems trying to do that from within a UIA 
Application (Script).
Any comments or pointers?
I am guessing you guys have had to deal with UIA for some time now and I am 
finding the learning curve via Googling and testing daunting and quite time 
consuming. 
Thanks for anything on this technical.
Rick USA

Reply via email to