On Fri, Mar 18, 2005 at 04:21:05PM +0900, Mike McCormack wrote:
> If you get rid of the thread, programs that don't run a message loop or
> that block for a time after receiving certain messages won't animate
> smoothly.
Yeah, I was half joking about removing it. comctl32 6.0 doesn't
run a threa
Dimitrie O. Paun wrote:
We should just get rid of the thread and the critical section altogether,
comctl32 6.0 is documented not to support it anymore. But before we do
that, let's try to fix this, so we have good code in CVS :)
If you get rid of the thread, programs that don't run a message loop o
On Thu, Mar 17, 2005 at 10:31:24PM +0100, Krzysztof Foltman wrote:
> The current CVS version has a regression in the animate control, causing
> a deadlock, most probably in WM_DESTROY handler, in the app I'm testing
> Wine with.
We should just get rid of the thread and the critical section altog
The current CVS version has a regression in the animate control, causing
a deadlock, most probably in WM_DESTROY handler, in the app I'm testing
Wine with.
trace:message:SPY_ExitMessage (0x10038) L"{SysAnimate32}" message
[0047] WM_WINDOWPOSCHANGED returned
trace:message:SPY_EnterMess
