[solved] @MSEC macro, Delayed update background?

[MvGulik]

Wondering about the seemingly delayed timed update that seems to be in effect with the @MSEC macro.

Test code:

For $i = 0 to 100
    DebugOut('@MSEC', @MSEC)
    Sleep(10)
Next

Output:

@MSEC = "359" {St} [0,0]
@MSEC = "375" {St} [0,0]
@MSEC = "390" {St} [0,0]
@MSEC = "390" {St} [0,0] ;; dupe
@MSEC = "406" {St} [0,0]
@MSEC = "421" {St} [0,0]
@MSEC = "437" {St} [0,0]
@MSEC = "437" {St} [0,0] ;; dupe
@MSEC = "453" {St} [0,0]
@MSEC = "468" {St} [0,0]
@MSEC = "484" {St} [0,0]
@MSEC = "484" {St} [0,0] ;; dupe
...

Edited September 11, 2011 by iEvKI3gv9Wrkd41u

[Melba23]

iE...,

I get just a few 11/12 returns when I run this - never anything less than 10.

$iLast = @MSEC - 10
For $i = 0 to 100
    $iNow = @MSEC
    $iDiff = $iNow - $iLast
    If $iDiff < 0 Then $iDiff = 1000 + $iDiff
    If $iDiff <> 10 Then
        ConsoleWrite($iNow & " - " &$iDiff & @CRLF)
    EndIf
    $iLast = $iNow
    Sleep(10)
Next

M23

Edit: I meant 10 not 0 - and yes it was before coffee time!

Edited September 11, 2011 by Melba23

[MvGulik]

Found additional topic about this.

*Reading up now.

---

... never anything less than 0.

... Think you forgot to take your morning coffee.

---

After experimenting with calling GetSystemTime() directly and searching MSDN I have found that this is a hardware limitation. The clock on most systems apparently, is only updated 64 times a second giving the 15 to 16 millisecond step observed.

Well, that kinda solves it.

Edited September 11, 2011 by iEvKI3gv9Wrkd41u

[JohnOne]

Since it will take a bit of farting about to get the script working from the OP, I tried M23s code a load of times

Occasionally get an 11, but most of the time nothing.

[MvGulik]

Think Bowmore has a good point here.

That means that this is definately not an AutoIt bug, but possibly the documation needs to be updated to point out this limitation.

If only to make sure its apparent that @MSEC should not be (fully) trusted to always give some unique data back.

(Right ... that only applies to cpu's that run at 1kHz or less of course ... )

Edited September 11, 2011 by iEvKI3gv9Wrkd41u