DDraw: Protect IDirectDrawImpl against race conditions

Stefan Dösinger stefandoesinger at gmx.at
Mon Dec 11 09:05:08 CST 2006

Am Montag 11 Dezember 2006 15:39 schrieb Alexandre Julliard:
> Stefan Dösinger <stefandoesinger at gmx.at> writes:
> > Am Donnerstag 07 Dezember 2006 21:17 schrieben Sie:
> >> This seems dangerous, changing the window size will potentially send
> >> messages to other threads, so doing it inside the lock can cause
> >> deadlocks.
> >
> > So I should unlock before I change the window size?
> Probably, though I guess that depends on what the Windows behavior is
> with windows and multiple threads.
I have to read up the msdn and propably write tests for it, but there are some 
methods which must be called from the thread that created the device. 
SetDisplayMode and RestoreDisplayMode are 2 examples, I *think* it applies 
SetCooperativeLevel too. It would make sense because SetCooperativeLevel is 
the method used to turn on multithreading protection.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-devel/attachments/20061211/8891701f/attachment.pgp

More information about the wine-devel mailing list