The GW-Scripting list is a discussion list for information regarding the development and use of Window-Eyes scripts. Any subscriber of the GW-Scripting list has the ability to post on-topic messages.

From:

 "BT" <b2me@fltg.net>

Subject:

 Re: KeyProcessedDown working

Date:

 Fri, Jun 1, 2012 8:06:14 am
This is a multi-part message in MIME format.

------=_NextPart_000_0015_01CD3FCD.6A57B1B0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Hi Rick,

Try starting here and see what you can find on the WMI stuff.

http://msdn.microsoft.com/en-us/library/windows/desktop/aa394572(v=vs.85).aspx

http://msdn.microsoft.com/en-us/library/windows/desktop/aa394589(v=vs.85).aspx

Sent: Friday, June 01, 2012 6:18 AM
Subject: Re: KeyProcessedDown working


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
------=_NextPart_000_0015_01CD3FCD.6A57B1B0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19222">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2 face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT size=2 face=Arial>Hi Rick,</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT size=2 face=Arial>&nbsp;&nbsp;&nbsp; Try starting here and see what
you can find on the WMI stuff.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT size=2 face=Arial><A
href="http://msdn.microsoft.com/en-us/library/windows/desktop/aa394572(v=vs.85).aspx">http://msdn.microsoft.com/en-us/library/windows/desktop/aa394572(v=vs.85).aspx</A></FONT></DIV>;
<DIV><FONT size=2 face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT size=2 face=Arial><A
href="http://msdn.microsoft.com/en-us/library/windows/desktop/aa394589(v=vs.85).aspx">http://msdn.microsoft.com/en-us/library/windows/desktop/aa394589(v=vs.85).aspx</A></FONT></DIV>;
<DIV><FONT size=2 face=Arial></FONT>&nbsp;</DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px"
dir=ltr>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, June 01, 2012 6:18 AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: KeyProcessedDown
working</DIV>
<DIV><BR></DIV>
<DIV><FONT size=2 face=Arial>Hi Chip: The setfocus to the File menu of the
MenuBar AutomationElement worked fine.</FONT></DIV>
<DIV><FONT size=2 face=Arial>I believe there is something called virtual focus
set on the last child AutomationElement that has focus whenever focus leaves
SolutionExplorer.</FONT></DIV>
<DIV><FONT size=2 face=Arial>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.</FONT></DIV>
<DIV><FONT size=2 face=Arial>From my readings so far the methods of handling
keyboard input are to use WM_Whatever and, or, monitor window
messages.</FONT></DIV>
<DIV><FONT size=2 face=Arial>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.</FONT></DIV>
<DIV><FONT size=2 face=Arial>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.</FONT></DIV>
<DIV><FONT size=2 face=Arial>Things get complicated quickly when looking at
WM_Whatever and cross-Process handling.</FONT></DIV>
<DIV><FONT size=2 face=Arial>Then there are the Message queus which may, or
not, offer a solution.</FONT></DIV>
<DIV><FONT size=2 face=Arial>Does anyone have a suggested methodology so I can
narrow a solution down to a single technical to start reading and
testing?</FONT></DIV>
<DIV><FONT size=2 face=Arial>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.</FONT><FONT size=2
face=Arial>Thanks</FONT></DIV>
<DIV><FONT size=2 face=Arial>Rick USA</FONT></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0015_01CD3FCD.6A57B1B0--