[Bug 10343] SetTimer won't wait for specified time

wine-bugs at winehq.org wine-bugs at winehq.org
Fri Nov 9 11:16:43 CST 2007


http://bugs.winehq.org/show_bug.cgi?id=10343





--- Comment #4 from jvlad <dmda at yandex.ru>  2007-11-09 11:16:43 ---
not exactly, how would it know timer IDs used somewhere in the application,
especially if they are not used up to the moment when SetTimer with NULL hWnd
is called? Windows solves this by assigning quite high values in assumption
that user uses quite low values for the timers he creates on non-NULL windows.

In details, suppose I have POLL_TIMER_ID=0x1 that I use for my main window.
Theoretically it's okay when SetTimer assigns 0x1 for the NULL window too
because I can capture window's WM_TIMER in its wndproc while NULL-ish timer can
be captured in the GetMessage loop. All is fine, except that window's WM_TIMER
is passed through the GetMessage loop too and since it has the same ID it may
create problems (and actually created them for me).


-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.



More information about the wine-bugs mailing list