Piotr Caban piotr@codeweavers.com writes:
I decided to leave 16-bit version of SetTimer as is for now. I haven't seen any application running out of window procedures in this case. This patch will change behavior of following 16-bit application: SetTimer(hWnd, TIMER_ID, 1, tfunc); GetMessage32(&msg, 0, 0, 0, TRUE); //get's WM_TIMER message DispatchMessage32(&msg, TRUE); Now this code will no longer call tfunc callback. According to my test new behavior is correct.
The more likely case is a 16-bit app retrieving a 32-bit timer and calling it through DispatchMessage16. How is this going to work with your proposed changes?