timerinit

[JohnMC]

so i just want to know more about this command, and when i did the following it didnt do what i expected, i would expect something around 2009 but got 1961, im probably making a simple mistake in how i break it down..

$var=TimerInit()
$var=$var/100;secs
$var=$var/60;mins
$var=$var/60;hours
$var=$var/24;days
$var=$var/365;years

MsgBox(0,"",$var)

[Melba23]

JohnMC,

I cannot fault the logic of the arithmetic, but I am not sure TimerInit necessarily uses the difference between NOW and midnight 1 Jan 1CE as the basis for its count!

If you want to get NOW, use the Date/Time macros (see in Help file).

The real value of TimerInit is to provide a timestamp which you can then use in TimerDiff to get the elapsed time since the TimerInit call. This works independently of the real time and so TimerInit can use whatever basis it wants as its start point.

M23

[JohnMC]

JohnMC,

I cannot fault the logic of the arithmetic, but I am not sure TimerInit necessarily uses the difference between NOW and midnight 1 Jan 1CE as the basis for its count!

If you want to get NOW, use the Date/Time macros (see in Help file).

The real value of TimerInit is to provide a timestamp which you can then use in TimerDiff to get the elapsed time since the TimerInit call. This works independently of the real time and so TimerInit can use whatever basis it wants as its start point.

M23

thank you, but thats kinda disapointing, im curious what it is based off of then... just curious

a script im planning out could benifit from using a timestamp in ms that translates to the real date/time so i supose ill construct a function to do just that especialy now the @MSEC is available...

Edited January 29, 2009 by JohnMC

[MvGulik]

whatever Edited February 7, 2011 by MvGulik

[Melba23]

MvGulik,

I have no idea what TimerInit uses as its basis. But I would only use TimerInit/TimerDiff for short (a few minutes at most) timings. Anything over that I would use _DateDiff, with calls to _NowCalc at the beginning and end of the period. That way you get a pretty accurate timing over long periods.

er

M23

[jchd]

AFAIK Windows precision timer use increments of 100ns on an unsigned 64-bit counter, originating at 19611601-01-01 (Windows epoch).

EDIT: I retyped 1961 blindly, but the actual value is of course year 1601. Sorry.

Edited February 23, 2010 by jchd

[PsaltyDS]

I think the native TimerInit() is similar to the UDF __Timer_QueryPerformanceCounter() in Timers.au3:

#include <Timers.au3>

$iTimer0 = __Timer_QueryPerformanceCounter()
$iTimer1 = TimerInit()
ConsoleWrite("$iTimer0 = " & $iTimer0 & @LF)
ConsoleWrite("$iTimer1 = " & $iTimer1 & @LF)