🚀 go-pugleaf

Read the doco ... SetTimer only has 55ms resolution (rounded up)
so (int)(1000/30) = 33 , which becomes 55ms which means if the
WM_TIMER message is never left in the queue then 90 WM_TIMER
msgs will take approx. 5 sec.  These are *not* real time OSs.
You should always check clock-ticks if accuracy is important. If you
really require 33 ms timers use multi-media timers, they can trigger
at 1ms intervals (but have associated overheads).

Good Luck

ChrisB2

Robin Burrows wrote in message <3619553C.11D5@bigfoot.com>...
>Hello,
>
>I'm trying to set up a timer with the following line:
>SetTimer (hwnd, 1, 1000/30, NULL);
>(30 interrupts per second) but the interval is nothing like that. For
>example, I process 90 interrupts which should take 3 seconds, but it
>takes more like 15. I am using a fprintf in my WM_TIMER, but the file
>remains open so the buffering should absorb it, there is no other
>lengthy code in there. What is the minimum gap between interrupts? Or am
>I just being dense? Do I really have to use GetTickCount and compensate
>for it myself?
>