> The OnTimer( ) handlers do *not* interrupt the GUI thread execution.
> They're called as part of the message looping, and no such reentrancy
> can occur. Of course if CExample objects are accessed from outside the
> GUI thread, then you should use normal interthread synchronization
> methods.
I believe that "no such reentrancy" is sightly inaccurate... agreed that
OnTimer() (the message version) doesn't interrupt the GUI thread, but if the
handler for a timer does something that allows message processing (manually
pumps messages to create a non-freezing pause, or even something as
"innocent" as putting up a message box), then another timer message CAN
re-enter the same code before the original has exited the routine.
In this particular scenario it can't cause problems with multiple accesses
to the same variable, but I felt it was important to clarify that it is
possible for WM_TIMER reentrancy in some circumstances.
--
Jason Teagle
[EMAIL PROTECTED]
