Rick, kdPass seems to be behaving as documented (that is, the program gets the keystroke but WindowEyes does not). The behavior you are seeing for kdProcess doesn't sound right, sounds like there's a problem somewhere. Chip
_____ From: RicksPlace [mailto:[email protected]] Sent: Sunday, June 17, 2012 6:11 AM To: [email protected] Subject: kdPass And kdProcess Hi I get unexpected results with OnKeyUp and OnKeyDown using the kdPass and kdProcess enums: When a script handles a keyboard OnKeyDown or up... I have kdPass and the underlying program seems to respond to keystrokes (I can see SolutionExplorer displayed and hidden upon the proper keystrokes) but WindowEyes speaks nothing. With kdProcess nothing seems to be getting through to the underlying program and WindowEyes speaks nothing. I filter the keyboard input on the running process id. I have no code inside the event handlers. I used WEEvent and it looks like the OnKeyDown and OnKeyUp events are being captured by WeEvent but WindowEyes speaks nothing for kdPass and nothing for kdProcess and with kdProcess seems to lock up the keyboard for most navigation and other keys although I can minimize the program but most keys do nothing including alt-f4 which should close the application. I have to shut down the computer to stop the program. Is this the normal behavior of the kdPass and kdProcess enums? Do I have to do my own WindowEyes Speech for both or is WindowEyes suppose to be speaking when kdPass and, or, kdProcess is being used? Should kdProcess not allow commands through to the underlying target program and not speak anything without explicit code to do these things? Rick USA
