Use a hidden window to catch the timer messages instead of a timer proc. This fixes...
authorRobin Dunn <robin@alldunn.com>
Fri, 24 Apr 2009 05:03:42 +0000 (05:03 +0000)
committerRobin Dunn <robin@alldunn.com>
Fri, 24 Apr 2009 05:03:42 +0000 (05:03 +0000)
commit9cfc7f4f68ab77a02cd855bf3ed1f88283af7d75
treeba3ee1f58de1d193bc9aabfdac1734c0d7705a27
parent9ca2956011cee803804c0df681d36213f9bc20d8
Use a hidden window to catch the timer messages instead of a timer proc.  This fixes an obscure problem where a new activation context is ignored while in the scop of the timer callback.  wxPython needs the activation context to always be active.

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@60296 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
src/msw/timer.cpp