bogus timer id in wxTimerProc

This assert message is occasaionally generated by timers in debug
builds of my app, even under seemingly normal conditions. It originates
from wxTimerProc in msw/timer.cpp. I wonder whether this should really
be considered reason for an assert message under MSW. The doc for the
Win32 KillTimer function explicitly states that it doesn't remove any
WM_TIMER messages already posted to the message queue. So, wouldn't a
call to Stop on a wxTimer around the same moment as when it should have
fired risk running into this situation?

-JM


---------------------------------------------------------------------
To unsubscribe, e-mail: wx-dev-unsubscribe@...
For additional commands, e-mail: wx-dev-help@...