 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. |
Determines if the implementation of the IMemInputPin::Receivemethod might block on the connected output pin.
Syntax
HRESULT ReceiveCanBlock(void); |
Parameters
None.
Return Value
Returns an HRESULTvalue, which can include one of the following values.
| Value | Description |
|---|---|
|
S_FALSE |
Input pin will not block on a Receivemethod. |
|
S_OK |
Input pin might block on a Receivemethod. |
Remarks
This member function implements the IMemInputPin::ReceiveCanBlockmethod. The base class implementation calls the IMemInputPin::ReceiveCanBlockmethod on the input pin connected to each of the filter's output pins.
This member function is useful because 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 be blocked, and might choose to start another thread to wait on the blocking Receivemethod.
See the COutputQueuebase class for queuing samples to input pins that potentially block.
Requirements
| Windows Embedded CE | Windows CE 2.12 and later |
| Windows Mobile | 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 |