Re: Confusing message from GraphEdit
- From: Geraint Davies <geraintd@xxxxxxxxxx>
- Date: Tue, 21 Nov 2006 13:52:57 +0000
On Mon, 20 Nov 2006 19:47:22 +0300, Taras P. Galchenko wrote:
I suppose there must be another reason. In my test program along with call
GetState to the filter graph I walked thru the list of the filters and asked
every filter for its state. All filters returned correct current state
without any error code, while the graph's GetState returned the correct
state value and E_FAIL.
Ok this indicates that a previous state transition failed. The state
transitions (e.g. from stop to run via a pause for cueing) are performed on
a background thread, after the original Run method has returned a success
code. If a filter then fails the Run method, the GetState would behave like
this.
G
.
- References:
- Confusing message from GraphEdit
- From: Taras P. Galchenko
- Re: Confusing message from GraphEdit
- From: Geraint Davies
- Re: Confusing message from GraphEdit
- From: Taras P. Galchenko
- Re: Confusing message from GraphEdit
- From: Taras P. Galchenko
- Confusing message from GraphEdit
- Prev by Date: wrong framerate rendering custom filter output
- Next by Date: Re: Flushing Through
- Previous by thread: Re: Confusing message from GraphEdit
- Next by thread: compilation issue of DS filter under vista
- Index(es):
Relevant Pages
|