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. |
Processes requests. This is a pure virtual member function.
Syntax
virtual LRESULT ThreadMessageProc( UINT uMsg, DWORD dwFlags, LPVOID lpParam, CAMEvent* pEvent ); |
Parameters
- uMsg
-
Request code.
- dwFlags
-
Optional flag parameter to request.
- lpParam
-
Optional pointer to extra data or a return data block.
- pEvent
-
Optional pointer to an event object.
Return Value
Any nonzero return causes the thread to exit. Returns zero unless an exit request has been processed recently.
Remarks
This pure virtual function must be overridden in your derived class. It is called once for each request queued by a call to the CMsgThread::PutThreadMsgmember function.
The member function defines the four parameters. Typically, use the uMsgparameter to indicate the request, and the other three parameters will be optional additional parameters.
The calling application can supply a pointer to a CAMEventobject in the pEventparameter if your application requires it. You must set this event after processing the event by using an expression, such as the following:
Copy Code | |
---|---|
pEvent->SetEvent |
One request code must be set aside to tell the worker thread to exit. Upon receiving this request, return 1 from this member function. Return 0 if you do not want the worker thread to exit.
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.