@lazlo: i guess the difference is that in the one example with "loop" the key is sent repeatedly, and in your example only one c-down is sent.
if you have a windows programm this might work as the key is repeated automatically. but perhaps the game does not recognize the c-down up but only checks for c-pressed ?
this means my example with settimer would also work if you change settimer ,...,20 to settimer, ...,0
but this looks like an endless-loop... (100%cpu ?!)
there is a difference in
keywait and
GetKeyState
a) Keywait. waits at this line in the programm until the "watched" key is pressed. like a "pause" (or sleep until key is pressed)
b) getkeystate only looks into the keybuffer if the key is pressed "now" (realtime) and returns immediately.
so they are not "functionally the same"
but using this loop thing is an endless loop and "bad" in my opinion (when there is no "sleep" in between as the cpu is constantly watching the keystate 100%cpu, which is nonsense.
my example would then look like this
Code:
$c:: ; prevent recursion with $
SetTimer, send_c_key , 0
keyWait, c , D ; currently is D, so waits for "next" D = toggle
SetTimer, send_c_key, off
return
send_c_key:
Send, {c}
return
actually settimer,...,0 means settimer,...,10 on window 2k or xp
Quote:
From SetTimer-Documentation:
Currently, timers cannot run much more often than every 10ms on Windows XP/2000/NT and about 55ms on Windows 9x. Specifying a Period less than this will usually result in an actual interval of 10 or 55 (but this policy could change in future versions so shouldn't be relied upon).
Login
Register
FAQ
Search
