Hi Rick,
Monitor the keydown event, set a flag and connect to the key up event.
Do nothing else. If you are doing something else, just place all of it in a
Queue routine, but not during the key down event.
Use the KeyProcess event for anything, if you want data, but only inside
a Queue routine call.
The connectevent should be only for a keyup event.
I will send you the code again for that. Just look at the key events or
list of events and place them at the beginning of your calling function
proc, (Call Back,) I had shown earlier.
Bruce
Sent: Friday, May 25, 2012 2:40 PM
Subject: Re: KeyProcessedUp and KeyProcessedDown Events
Hi Steve:
I just want the normal things to happen when I click Shift-Escape to hide
the Solution Explorer Window.
WE does not recognize it has been hidden.
When I use Event Handlers to watch for the KeyProcessedDown and
keyProcessedUp events 2 things happen:
1) The normal processing does not take place, in other words, the screen
does not go dark and Solution Explorer seems to still have focus.
2) The KeyProcessedDown key handler fires but the following
KeyProcessedKeyUp does not fire.
Actually it fired in a test where I had acoding error and created multiple
copies of the handler but when coded correctly it does not appear to fire
and the normal processing of hiding Solution Explorer does not take place.
This is sounding more and more like a WE Problem Bruce had described in a
previous post.
so I will have to dig into his VBS solution to see if I can adapt it to my
external script for another test tomorrow or this weekend.
By the way, the ActiveWindow and FocusedWindow elements do not change after
the KeyDown event fires as I would expect from some testing in the WE
Immediate Window so something appears to be not allowing the normal
processing to take place when I use the KeyProcessedDown event handler which
does fire correctly on the Shift-Escape key press.
Anyway, I will have to download Bruces code base and go through it to see
what he did to get around this problem if I can.
Rick USA
