On Fri, 10 Feb 2006 14:43:09 +0100 -JM <
jm@...> wrote:
J> This assert message is occasaionally generated by timers in debug
J> builds of my app, even under seemingly normal conditions. It originates
J> from wxTimerProc in msw/timer.cpp. I wonder whether this should really
J> be considered reason for an assert message under MSW. The doc for the
J> Win32 KillTimer function explicitly states that it doesn't remove any
J> WM_TIMER messages already posted to the message queue.
AFAIK WM_TIMER messages are not posted to the queue, they're artificially
generated when the timer expires and the application is ready to process
them. So I find it somewhat surprizing that there are any timer messages
remaining in the queue. But if this is really the case we should be able to
remove them with PeekMessage().
J> So, wouldn't a call to Stop on a wxTimer around the same moment as when
J> it should have fired risk running into this situation?
Can you reproduce this in a simple example?
Regards,
VZ
---------------------------------------------------------------------
To unsubscribe, e-mail:
wx-dev-unsubscribe@...
For additional commands, e-mail:
wx-dev-help@...
