WM_TIMER - different thread, separate entity?
Posted on 2006-06-05
Does SetTimer open a new thread? If not, can anyone explain to me why AfxMessageBox inside of OnTimer does not prevent further calls to OnTimer? In other words,
The message box appears... and then appears again, and again, without waiting for me to close the first one. It's like Windows is trying to process the next WM_TIMER message without waiting for the current on to complete.
If this is what happens, is there a normal way to prevent it? In other words, how can I block the timer without actually killing it?