This is the interface for the LEAD ONVIF Source filter.
This filter can be controlled by using this interface and by passing parameters in the ONVIF Source URL. For more information on the URL parameters, refer to ONVIF Source URL Syntax.
The user callback that will be called when certain events occur. At the moment, there is only one event (EVENTTYPE_NODATAAVAILABLE), which indicates the source filter has not received any data. You can use this callback to receive notifications indicating no data is arriving and cancel the wait.
The user callback object should implement the ILMSrcCallback interface.
LEADTOOLS uses this interface internally when you load a stream using the UDP source filter. The Play and Convert objects will automatically intercept the ILMSrcCallback notifications and will send the ltmmEC_LOADSTATUS event with the ltmmAM_LOADSTATUS_WAITING_FOR_DATA notification to inform you when EVENTTYPE_NODATAAVAILABLE is fired by the ONVIF source. In other words, you do not need to implement the ILMSrcCallback interface to take advantage of this feature. For more information, refer to Aborting Loading From The RTSP, ONVIF, and UDP Source Filters.
|VARIANT_BOOL||CallInSameThread||Enables or disables the calling of the CallbackProc notifications in the same thread that set the ReceiveProcObj property. Possible values are:|
Call the notifications in the same thread that set the callback. This reduces the performance and requires the application to process messages, otherwise the callback will not get called. It is the default and is required for platforms that have problem with multithreading, like VB 6.0, MFC or DotNet.
This is the default.
|VARIANT_FALSE||Call the notifications in any thread of the process. Use this setting for best performance in platforms that can handle this. This is the recommended mode for C++ applications. But you should be aware that your callback will not be called in the main thread, so you need to take care when you interact with the user interface.|
Medical Web Viewer .NET