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. |
Provides access to properties and methods exposed by an object.
Syntax
HRESULT Invoke( DISPID dispidMember, REFIID riid, LCID lcid, WORD wFlags, DISPPARAMS* pdispparams, VARIANT* pvarResult, EXCEPINFO* pexcepinfo, UINT* puArgErr ); |
Parameters
- dispidMember
-
Identifier of the member. Use CBaseBasicVideo::GetIDsOfNamesor the object's documentation to obtain the dispatch identifier.
- riid
-
Reserved for future use. Must be IID_NULL.
- lcid
-
Locale context in which to interpret arguments.
- wFlags
-
Flags describing the context of the CBaseBasicVideo::Invokecall.
- pdispparams
-
Pointer to a structure containing an array of arguments, an array of argument dispatch IDs for named arguments, and counts for number of elements in the arrays.
- pvarResult
-
Pointer to where the result is to be stored, or NULL if the caller expects no result.
- pexcepinfo
-
Pointer to a structure containing exception information.
- puArgErr
-
Index of the first argument, within the rgvargarray, that has an error.
Return Value
Returns DISP_E_UNKNOWNINTERFACE if riidis not IID_NULL.
Returns one of the error codes from CBaseBasicVideo::GetTypeInfoif the call fails.
Otherwise, returns the HRESULTfrom the call to IDispatch::Invoke.
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 |
Internal Server Error
The 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.