Microsoft DirectX 9.0 |
This topic applies to Windows XP only.
In a television application, various objects send events, including the Video Control. The application can listen for these events and respond to them. For example, the Video Control sends an event when the video window is clicked or receives a keystroke.
Objects send events using COM connection points. To catch an event, the client implements an event interface. The object fires events by calling methods on that interface. For example, the Video Control sends events through the _IMSVidCtlEvents interface. The mouse-click event is _IMSVidCtlEvents::Click.
In COM terminology, the event interface is the outgoing interface, the object that sends the events is the source, and any object that receives events is a sink. Typically the outgoing interface is a dispinterface, so the sink must implement IDispatch. The source fires events by calling IDispatch::Invoke with the dispatch identifier (dispid) of the method.
To receive events:
The following code sets up the connection point between the client and the Video Control:
HRESULT hr;
DWORD dwCookie;
CComPtr<IMSVidCtl> m_pVideoControl; // Pointer to the Video Control.
// Query the Video Control for IConnectionPointContainer.
CComQIPtr<IConnectionPointContainer> pContainer(m_pVideoControl);
if (pContainer)
{
// Find the connection point.
CComPtr<IConnectionPoint> pConnectPt;
hr = pContainer->FindConnectionPoint(DIID__IMSVidCtlEvents,
&pConnectPt);
if (SUCCEEDED(hr))
{
// Get the IUnknown pointer of the event sink, which is
// typically the client itself.
CComQIPtr<IUknown> pUnk;
this->QueryInterface(IID_IUnknown, (void**)&pUnk);
hr = pConnectPt->Advise(pUnk, &dwCookie);
}
}
The Advise method returns a token (also called a cookie) that identifies the connection. The source object continues to fire events until the sink breaks the connection. To break the connection, call the IConnectionPoint::Unadvise method and pass in the same token:
hr = pConnectPt->Unadvise(dwCookie);