----- Original Message ----- From: "Gerard Patel" <gerard.patel(a)nerim.net> To: "Guy L. Albertelli" <galberte(a)neo.lrun.com> Cc: <wine-devel(a)winehq.com> Sent: Saturday, November 10, 2001 2:14 AM Subject: Re: Regression errors
At 12:38 AM 10/11/2001 -0500, you wrote:
1. SetTimer call is not always generating WM_TIMER messages as it should. I see:
0806bb20:Call user32.SetTimer(00020057,00001003,00000000,6003a04c) ret=6001e9e4 0806bb20:Ret user32.SetTimer() retval=00001003 ret=6001e9e4
in the trace, but never is the callback routine invoked. Without the above patch, the callback is invoked and does the painting.
I am not sure if it's related, but I have seen something like that. I have seen it since much longer than this patch, though.
It's about the paint count in the server. When there is a paint count > 0 in the server and the number of windows found to need a repaint (at the client level) is less than the paint count, the client can never get a timer event again.
Try this patch to dlls/user/message.c to see if your problem is related :
Thanks Gerard. I will try it Tuesday. Going out of town till then. Guy