That may be that things have changed. However, something must be
decrementing (incrementing) each and every timer. And I don't know if that's
still done in response to the PC's clock tick interrupt. If so, I would
"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
Just to check it out, I created a whole bunch of windows, and in each
window, I did a
SetTimer. I created 7426 windows before I ran out of memory (GetLastError
= 14), and each
one had a timer. SetTimer failed to return 0 at any point in this
exercise. This
suggests that the idea that timers are a limited resource is erroneous,
and merely
leftover folklore from Win16 (where they were limited; in that system you
couldn't have
more than 4 timers in Windows 3.0 and 8 timers in Windows 3.1).
I'm not sure that 7426 is a valid upper bound; I had just run a test in
which I created
162,000 files, but I have discovered that my system has become quite
sluggish, so the
upper bound may be inherited from my pre-trashing the kernel with massive
file counts.
joe
On Mon, 10 Jul 2006 20:10:07 -0600, "Jonathan Wood"
<jwood@softcircuits.com> wrote:
Timers are a limited system resource. For this task, I would definitely
kill
the timer whenever the mouse leaves your window. Just start the timer
whenever it enters.
Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm