>
> a bad loop, it will most likely eat processortime
Well, 0% CPU isn't much processor time for such a tight loop.

I said using HK's is a bad approach since it can interfere or as you state fail to initialize die existing HK.DoubleDutch wrote:I don't understand what you mean, the result will mean that your request has failed - so pick another key.Can be, therefore it remains a bad scenario..
What does "Can be, therefore it remains a bad scenario" mean???
-Anthony
Hmm, i don't know how this behavious exactly.PB wrote:>> Repeat : Sleep_(1) : Until GetAsyncKeyState_(#VK_F1)<>0
>
> a bad loop, it will most likely eat processortime
Well, 0% CPU isn't much processor time for such a tight loop.
me too!KameHameHaaa wrote:I have to intercept any mouse movement, keyboard press, to launch an event after some time of inactivity, just like the task that launches a screensaver...
I found that you can capture mouse movement globally with DesktopMouseX() and DesktopMouseY() - even when the application looses focus, this seems to continue to work. (at least on Windows, haven't had the opportunity to test with Linux)KameHameHaaa wrote: Is it possible to use GetAsyncKeyState for any key instead to check ANY possible key?
What about mouse movement?