Hi BT: That is the event handler I have used all along. I wanted the normal operation of the shift-escape key so I elected to use the Key Object's KeyProcessed Event Handlers. I tried using the Keyboard Regestering method of setting the CursorKey and then used the Key Property, think it was a property, to get at the KeyProcessed handlers. I tried many methods but even though the handler event sub fired fine the screen did not go dark as it did when the handler sub was not executed even with no code inside the sub at all. Steve and Chip wanted me to try the CursorKey another way I think so I decided to make a SetFile and use the CursorKey definition from within the SetFile. The CursorKey Handler is again firing but I cant see the screen well enough yet to tell if it is going dark as it should or not as it did testing other methods. Rick USA
----- Original Message ----- From: BT To: [email protected] Sent: Sunday, May 27, 2012 2:40 PM Subject: Re: KeyProcessedUp and KeyProcessedDown Events Hi Rick, Yes, that is my next move with my Star Trek game, having it's own set file. I was wondering though, did you every try the OnKeyProcessedDown event? I know you had done the key down event, but did you try the processed one which makes sure that key has already been processed and any thing going on, such as the screen going dark, would have been done at that point. Bruce Sent: Sunday, May 27, 2012 2:17 PM Subject: Re: KeyProcessedUp and KeyProcessedDown Events Hi Chip: that was the first method I tried per your and Steve's suggestions a few days ago. It fired but the screen did not go dark when using the handler. Then I tried mucking with the KeyProcessedKeyUp event handler as to Bruces ideas. It didn't work So this time I added Shift-Escape to the VB2010Express.set SetFile and access it from my script. Then I set up the event handler and, again as with the Keyboard Registration method, it is firing properly but I cant see if the screen is going dark as it should - too light in here right now. I think the method I am trying now is the only other way to handle this key press from within WindowEyes without resorting to some ugly hot key solution. Later and I will make some noise if things are working using the SetFile Method of getting at the CursorKey.Key Event handlers. At least I learned how to work with a SetFile from within an external script. Rick USA ----- Original Message ----- From: Chip Orange To: [email protected] Sent: Sunday, May 27, 2012 1:54 PM Subject: RE: KeyProcessedUp and KeyProcessedDown Events Hi Rick, I think I didn't make my point well. Check out the keyboard object's registerCursorKey method; it's just like registering a hotkey, except the application program gets to see the keystroke as well as your app (which is what you want in this case). Chip ------------------------------------------------------------------------ From: RicksPlace [mailto:[email protected]] Sent: Saturday, May 26, 2012 9:05 PM To: [email protected] Subject: Re: KeyProcessedUp and KeyProcessedDown Events Hi Chip: I used the KeyProcessed Event Handlers. I picked up the Key Object from the Keyboard Object instead of from a CursorKey object which I think is the same Key object but defined in diferent places. That said I see where a CursorKey itself might offer the execution of the first and second event without impacting the Target Application since it is a WE operation. Perhaps it's Key Object is somehow diferent than the Keyboard Object's Key Object. I am thinking of defining a CursorKey in the We Dialog with undefined actions and then accessing it in my script where I can tweak the scope and action properties which are likely irrelevant to this requirement but may be somehow helpful. Then I can pull the Key Property from the CursorKey object. What about the actions? I have never worked with Actions but an action might not require an event handler. Otherwise can you or Steve give me an idea of how best to define a CursorKey to work with from within an external script? I should think the Key object is going to have the same problematic event handlers in the KeyProcessed Events but I will try out your suggestions if I can define a CursorKey to use. Any suggestions on adding one to the WE Dialog and using the Keys Object to then pkull it into my script? Rick USA. from ----- Original Message ----- From: Chip Orange To: [email protected] Sent: Saturday, May 26, 2012 12:13 PM Subject: RE: KeyProcessedUp and KeyProcessedDown Events Rick, Steve and I have both suggested you use a cursor key for this (it prevents any possibility of effecting the underlying program); Bruce suggeested the same idea with the onKeyProcessed event. I don't see why you would pass these over. Chip -------------------------------------------------------------------- From: RicksPlace [mailto:[email protected]] Sent: Saturday, May 26, 2012 9:18 AM To: [email protected] Subject: Re: KeyProcessedUp and KeyProcessedDown Events Hi Bruce: I ran some more tests and found that when I closed all windows I could still tab around to the buttons for hidden items of varying sorts. Also, Automation Focus tracked the Tab item being found. It appears that what is shown depends on the Selected Item in the Tab Group rather than what has focus. So I will be trying to figure out how to work with the Selection Pattern or the SelectionItem patterns to see if there is anything there. What a friggen pain in the colon! Rick USA
