"Christian Costa" <[EMAIL PROTECTED]> wrote:
> >If the MCI command was sent asynchronously (without MCI_WAIT)
> >an thread gets created and the command gets executed there.
> >
> >So, if an app does:
> >mciSendCommand(MCI_PLAY); // an async thread gets created
> >and right after that:
> >mciSendCo
Dmitry Timoshkov wrote:
"Christian Costa" <[EMAIL PROTECTED]> wrote:
Are you sure this is usefull.
How can SetEvent cause a deadlock?
That's exactly the same case your recent patch has fixed.
My patch was intended to fix a deadlock with the thread of the wave
driver not with the async o
"Christian Costa" <[EMAIL PROTECTED]> wrote:
> Are you sure this is usefull.
> How can SetEvent cause a deadlock?
That's exactly the same case your recent patch has fixed.
If the MCI command was sent asynchronously (without MCI_WAIT)
an thread gets created and the command gets executed there.
So
Hi Dmitry,
Are you sure this is usefull.
How can SetEvent cause a deadlock?
Bye,
Christian
> Message du 16/03/04 14:54> De : Dmitry Timoshkov <[EMAIL PROTECTED]>> A : [EMAIL PROTECTED]> Copie à : > Objet : Avoid a possible deadlock when stopping playback> Hello,> >
