See Also
 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
This method determines if the implementation of the IMemInputPin::Receivemethod might block on the connected output pin.
Syntax
HRESULT ReceiveCanBlock(void); |
Parameters
None.
Return Value
Can return any HRESULTvalue.
The following specific success values can be returned.
| Value | Description |
|---|---|
|
S_FALSE |
Input pin will not block on a Receivemethod. |
|
S_OK |
Input pin might block on a Receivemethod. |
Remarks
An output pin from a filter might require notification if its thread might be blocked when it calls the Receivemethod on the connected input pin.
For example, a source filter might prefer to keep reading and buffering data rather than to be blocked, and may choose to start another thread to wait on the blocking Receivemethod.
If your implementation of Receivecalls a downstream filter's Receivemethod on the same thread, the application will block if that filter blocks, and this method must indicate that.
Requirements
| Windows Embedded CE | Windows CE 2.12 and later |
| Windows Mobile | Pocket PC for Windows Mobile Version 5.0 and later, Smartphone for Windows Mobile Version 5.0 and later |
| Note | Microsoft DirectShow applications and DirectShow filters have
different include file and Library requirements
For more information, see Setting Up the Build Environment,Version 2.12 requires DXPAK 1.0 or later |