Wow, we need some inside win assembler to understand this ;)
You can have a killtimer, but which timer will you kill???

Maybe is a bug? you know, you found a way to fill up memory without any control.. can we make a virus of it??? ;) also you will fill up the msg queue!
Seriously, I don't have any idea beyond what I posted, but now I want to know!

HTH

Gonzalo

================================================== =========
Read this if you want to know how to get a correct reply for your question:
http://www.catb.org/~esr/faqs/smart-questions.html
^^Took that from dparsons signature and he Took that from planoie's profile
================================================== =========
My programs achieved a new certification (can you say the same?):
WORKS ON MY MACHINE
http://www.codinghorror.com/blog/archives/000818.html
================================================== =========
I know that CVS was evil, and now i got the proof:
http://worsethanfailure.com/Articles...-Hate-You.aspx
================================================== =========

When you use SetTimer, it returns an ID. You need to use that ID to use KillTimer—it's a required argument.

These nuts-n-bolts issues can indeed be interesting.

It's also really enjoyable to me to examine an issue like this with others who can recognize the architecture which underlies the daya to day IDEs we use. Thanks to all who have participated for a refreshing exchange!