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 retrieves the name and media type of the current file.
Syntax
HRESULT GetCurFile( LPOLESTR* ppszFileName, AM_MEDIA_TYPE* pmt ); |
Parameters
- ppszFileName
-
[out] Address of a pointer that receives the name of the file, as an OLESTR type.
- pmt
-
[out] Pointer to an AM_MEDIA_TYPEstructure that receives the media type. This parameter can by NULL, in which case the method does not return the media type.
Return Value
Returns an HRESULT value. The following table shows some possible values.
Value | Description |
---|---|
S_OK |
Success. |
E_FAIL |
No file is opened. |
E_OUTOFMEMORY |
Insufficient memory. |
E_POINTER |
NULL pointer argument in ppszFileName. |
Remarks
If the filter has not opened a file, the method might succeed but return NULL in the ppszFileNameparameter. Check the value when the method returns.
The method allocates the memory for the string returned in ppszFileName, and the memory for the format block in the media type (if any). The caller must free them by calling CoTaskMemFree. For the media type, you can use the FreeMediaTypefunction in the base class library.
Requirements
Windows Embedded CE | Windows Embedded CE 6.0 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 See AlsoInternal Server ErrorThe server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error. More information about this error may be available in the server error log. Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request. |