Freigeben über


ISpNotifyCallback (Windows CE 5.0)

Send Feedback

This interface allows the application to receive notifications. It is not a COM interface, but is a C++ virtual interface that can be implemented by the application. Because it is not a COM interface, the application does not need to implement QueryInterface, AddRef, or Release.

It is the responsibility of the application to control the lifetime of an ISpNotifyCallback-style notification. To remove an installed notify callback, call ISpEventSource::SetNotifySink. The final release of an object that supports ISpEventSource will automatically remove an installed notify callback.

When to Implement

The SAPI implementation uses a hidden window to call back the client on the same thread that was used to initialize the event source. Notification callbacks are the result of processing a window message. This means that when the notification mechanism is used:

  1. The NotifyCallback method will always be called on the thread that initialized the event source or notify translator object.
  2. The thread must have a window message pump.

Methods

The following table lists the methods for ISpNotifyCallback.

Methods Description
NotifyCallback Supports callbacks from an object that supports ISpEventSource when an event occurs.

Requirements

OS Versions: Windows CE .NET 4.1 and later.
Header: Sapi.h, Sapi.idl.
Link Library: Sapilib.lib.

See Also

SAPI Interfaces

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.