🚀 go-pugleaf

A couple of things:

1) The standard timer is driven by the standard BIOS timer tick, so you
can't generate more than 18.2 timer events per second using SetTimer. To go
faster, you'll have to use the multimedia timers (see the timeSet*
functions, etc.)

2)If the timer generates another tick before your app has processed the last
WM_TIMER message, it will NOT put another one on the queue. Also, WM_TIMER
messages are low priority, and will only be given to your app if there are
no other messages on the queue.

--
//
// reply to:
// BgPorter at acm dot org
//
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?
>