HI
> 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.
>
I beleive the same can happen simply with you running a piece of code, that
also gets run by a screen update type message etc. I had to use a bool as a
flags to get around this.
Regards
Max
