🚀 go-pugleaf

Robin Burrows wrote:
> 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?


Greetings.

I share the opinions of the people who already responded. I'ld like to
add though that I find this a strange way to print. Probably your
concern is to to not block the main thread - which would result in
'blank' pieces of screen waiting to be updated during the printing
process, and the user would not be able to do anything. There are
several other, proper, ways to take case of this. Do the printing in
another thread. This is by far the best way, but also not very easy if
you didn't do this before. The ProcessMessages is a far easier way out:
encapsulate the timer code in in a loop, and do a ProcessMessages after
each loop.



Joris Van Damme
ecogreen.joris.vandamme@ping.be