_Timer_GetIdleTime issue

[Carlo84]

Hello i needed a function to detect userinput

1st i tried using:

 GUIRegisterMsg($WM_KEYDOWN, "_Exit")
 ($WM_KEYUP, "_Exit")
GUIRegisterMsg($WM_MOUSEMOVE, "_Exit")

But that doesnt work once there are controls on the GUI

 

so i came to find _Timer_GetIdleTime()

 

but the issue here is that after user activity it does the following:

1. it resets to zero (as it should)

2. it starts counting again (as it should)

3. at 5000 it resets. (theres my issue)

4. it counts again without resetting at 5000

 

why does it reset a second time without user activity?

 

example to recreate the problem:

#include <Timers.au3>
#include <GUIConstantsEx.au3>

GUICreate('_Timer_GetIdleTime', 512, 256)
GUISetState(@SW_SHOW)
$hLabel = GUICtrlCreateLabel('', 10, 10, 256, 25)
$iTime = _Timer_GetIdleTime()
While 1
    $iMsg = GUIGetMsg()
    If $iMsg = $GUI_EVENT_CLOSE Then Exit

    $iTime = _Timer_GetIdleTime()
    $iExtended = @extended
    GUICtrlSetData($hLabel, $iTime & '   ' & $iExtended)
WEnd

Have searched the forums but haven't been able to find anyone with the same specific issue. Edited October 15, 2013 by Djarlo

[BrewManNH]

It works fine for me. I let it run, it counts up. I move the mouse it resets. I stop moving the mouse and it counts up, it never stops at 5000 and resets for me. It might have something to do with the information in the remarks section on this page.

 

The tick count when the last input event was received (see LASTINPUTINFO) is not guaranteed to be incremental. In some cases, the value might be less than the tick count of a prior event. For example, this can be caused by a timing gap between the raw input thread and the desktop thread or an event raised by SendInput, which supplies its own tick count.

[Carlo84]

It works fine for me. I let it run, it counts up. I move the mouse it resets. I stop moving the mouse and it counts up, it never stops at 5000 and resets for me. It might have something to do with the information in the remarks section on this page.

Thanks, should have looked it up on msdn indeed, helpfile doesn't have this part.

And checking for each key is more code then it's worth, i think ill just settle on monitoring mouse movement it's simplest and seems the most reliable method.

[BrewManNH]

I found the information by looking at what the function does internally. Looking at the DLLCall statement and searching for the function that is used in the DLL to get the information.

Local $aResult = DllCall("user32.dll", "bool", "GetLastInputInfo", "struct*", $tStruct)

So, looking at that line, I googled "GetLastInputInfo" and started to look at what was returned from MSDN. Most of the time when reading the MSDN pages I get horribly lost as to what the function does, but once in a while I can get something from them.