Introduction

Discontinuation

2018 releases will be the last MIP SDK releases to include the following components: ImageViewer, AudioPlayer, EngineManager ActiveXs and the "UseActiveX" environment option.

Existing applications using these components should not be affected during 2018 since maintenance work on these components will continue until 2019 R1, but with no new functionality added.

With MIP SDK 2019 R1 these components will be officially discontinued and will no longer be included in the MIP SDK. For Web and C++ development, we strongly recommend developers to already now start using the Mobile Server interface instead. As for Windows based applications, we recommend using the ImageViewerControl or ImageViewerWpfControl .NET controls.

MIPSDK General

• Support for displaying MIP SDK plug-in items on Smart Map:
  • MIP plug-in elements can be placed on the Smart Map with a custom icon either programmatically or using the Smart Client. They can also be associated with buildings and floors of a building.
  • Multiple MIP plug-in elements that are located close to each other will be clustered, depending on current zoom level and kind.
  • Context menus (right-click in Smart Client) and actions on MIP plug-in elements can be defined and localized.
  • Existing MIP plug-in elements that support the bitmap style maps in Smart Client will now also be available on Smart Map.
  • Server.MipItemPositionChangedIndication message can be utilized to be notified whenever a MIP plug-in element has an updated position.

Component Integrations

• Breaking change due to introduction of a new Log Server component
  The 2018 R3 release of XProtect introduces a new Log Server together with new log clients. The old client residing in VideoOS.Platform.SDK.Log.dll is no longer able to read logs from the new Log Server. Existing solutions that use the LogClient class and were built with 2018 R2 or earlier versions of the MIP SDK need to be rebuilt using the 2018 R3 release of the MIP SDK. The API has not changed.

Configuration API

• MIP kinds and items can now be added, updated and removed through the Configuration API.

Samples

• Transact Client sample added, demonstrating how to select an XProtect Transact source, and then showing live updates of the latest transactions as well as searching for transactions.
• Sensor Monitor sample has been updated to include support for localization of kinds and right-click menu items, which is utilized by the new Smart Map MIP support.

Fixed issues

• When SaveItemConfiguration was called twice very quickly in the Event Server it could result in an error log message. It could also happen that some of the items were not saved correctly.
• Calling the Update methods on AlarmCommand would update content three times.
• An Event Server background plug-in can now obtain the Video Wall monitor and presets and Smart Map locations.
• Changing one of the security permission properties on a camera, for example, would cause the property to be duplicated instead of having its value changed.
• When updating the frequency interval setting for an archive storage schedule, this would always be evaluated towards the settings allowed for the MonthlyRelative type, no matter what the actual type was, meaning that some valid settings would not be allowed.
• If you logged in to the VMS using another Windows user than the one currently logged on to Windows, the LogClient would still register the log with the current Windows user.
• When subscribing to the ApplicationModeChanged message and entering into Setup mode in the Smart Client you would be notified with the mode ClientPlayback instead of ClientSetup.