Hi: I created a hot key to print whatever window properties are under the mouse when clicked. OK: To test it I ran VS to the DeadSpot, routed the mouse to the cursor and hit my script hot key. As soon as I did, the print finished and the MsgBox popped up "Done" focus in the VS Program returned into the TextEditer and did not stay in the DeadSpot. Now, since the script has nothing to do with Visual Studio there should have been no activity within the VS Process and thus things should not have changed inside the VS program. There is one possibility that even though I filter the MSAA on the process the OnChildFocus is not filtered if I get it right and I did connect originally to the Desktop. To determine what happens just after hitting the hot key I thought I might monitor the WEEvents but is there a way to know when I hit the script hot key in the WEEvent Output? Perhaps one of the settings? I am also getting some unusual, unexpected, results but in general it looks like when DeadLocked the screen point is outside the text being edited but I have not found any window rectangles including the ClientArea that indicate anything except what looks like the entire screen and perhaps then some. So this is one way I might be able to associate what happens when focus returns to the Editer after executing a hot key in my script if there is a way to indicate it in the WEEvent output, just don't know and am running out of ideas - getting brain dead. Rick USA
_______________________________________________ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com
