joerg-cyril.hoe...@t-systems.com a écrit :
Eric,
I wrote:
However, it[Wine's MCI] still hangs in the full tests. I believe the last bug
in mciwave
will only be nailed down once the play and record loops manage to talk robustly
with other commands such as pause and close.
A recent ide
Eric,
I wrote:
>However, it[Wine's MCI] still hangs in the full tests. I believe the last bug
>in mciwave
>will only be nailed down once the play and record loops manage to talk robustly
>with other commands such as pause and close.
A recent idea of mine is to build upon your thread split work a
Eric,
I now tested you 2 "async split" patches on a pristine 1.1.31, i.e. without
any of my patches. It is a good idea and astep in the right direction. The
next step would be to move all possible tests before the split point,
e.g. return OUTOFRANGE for bad positions.
However, it still hangs in
Eric,
I've not yet tested your patches but I thought to additionaly use
STATUS_NOT_READY
as an intermittent marker for work in progress, so other threads know something
is going on and don't pull the carpet under the feet. What do you think?
E.g. play; play from 0; play from 1000; play from 0; se
