[RESOLVED] GetAsyncKeyState

[Mr.Mac]

I've been playing with this, and have writting a nice program for my own use.

This program, however, is designed to stay open while I go do other stuff.

My problem: I can be in an entirely different window, yet if I hit one of the keys my program is reading, it tries to process it, causing great confusion to me.

So I am looking for

GetAsyncKeyStateButOnlyIfMyWindowIsActive

LOL

or, failing that, a test to see if my window is active. I could put that in the timer loop to ignore everything unless I am active.

Or maybe there is a better way? For example, a SUB to get control when my program becomes inactive (which could turn off the timer) and another one when it becomes active again (to turn timer on)

[triggernum5]

Any reason why KeyDown/KeyUp events aren't sufficient? Thats the path of least resistance.. Aside from that, just nest your GetAsyncKeystate inside a GetWindowPos type IF statement..

[ixtrip]

You could try to use GetForegroundWindow

Public Declare Function GetForegroundWindow Lib "user32" () As Long
 
if GetForegroundWindow = me.hwnd then
'top window
else
'not top
end if

And throw it into a timer? Doesn't use up too much memory :-P I'm trying to think of somethin else but i would try keydown, keyup first...if i think of anything i'll throw it in here..

[Mr.Mac]

Any reason why KeyDown/KeyUp events aren't sufficient

n00b = Mac

Actually, first I saw some stuff about GetAsyncKeyState and then I wrote a program around it just to see how it works and forgot that I didn't have to do that.

But after your suggestion, I ripped out all the TIMER/GetAsyncKeyState stuff and replaced it with KeyDown/KeyUp stuff. MUCH SIMPLER!!!

Thanks!!

Mac

[ixtrip]

You learn somethin new everyday ;-)

[Mr.Mac]

You learn somethin new everyday ;-)

LOL - Yep.

What didn't occur to me was that the GetAsyncKey stuff was really intended to get keypresses when you program was NOT in control. For example, a key logger. Or a program to wait for hot-keys and then initiate something.

It had no utility at all for a program that was in control. That program could simply read key events the normal way.

Oh, well. Live and learn. Actually, live and learn what you once knew already.

Mac

[triggernum5]

Actually, remember for the future that hotkeys have their own APIs.. RegisterHotkey and UnregisterHotkey IIRC.. Although you could build your own system with GetAsyncKeystate.. GetAsyncKeyState can go pretty hardcore if you dive into complex params..