Release Notes > December 2025 Release 1

New Features:

•Further overhaul of web-based UI design

•Additional Database callback mechanism - refer to BncsDatabase.AddSlotCallback()

Breaking Changes:

•BncsChangeEventActions the Abort value has been renamed to Reverse to better describe the internal handling of the action

Bug Fixes:

•BST-2054/DDK-84/DDK-16 – Corrected behaviour of IW & IR issuance. Also updated web/api behaviour to be more consistent with bCommand.

•BST-2051/DDK-82 – WebUI/API infodriver view changes now correctly update linked parameters & vice-versa

•BST-2047 – Default options now parse correctly – uint type options changed to int

•DDK-53 – Introduced interfaces to represent Managed & Monitored infodrivers masking the appropriate change notification events to avoid confusion.

•DDK-48 – UI: Current log file now downloadable via UI

•DDK-98 – UI: Debug level log information now available in the UI log viewer

•DDK-99 – UI: Log banner is now resizable

•DDK-100 – UI: Enum dropdown now available in UI instead of numeric

•DDK-105 – UI/logging: Log files now contain log level data

•DDK-86 – UI: Log view correctly scrolls to latest log entry

•DDK-80 – UI: Fixed formatting of UI Header

•DDK-87 – UI: Log download feature now working

•DDK-72 – UI: Modal popup displays when background driver task closed. Reconnect supported

•DDK-39 – UI: Infodriver view dropdown list now populated automatically on first page load

•DDK-32 – UI: All UI validation error believed fixed

•DDK-83 – UI: Tab page state now persisted

•New option to enable/disable automatic display of web UI on startup

Known Issues:

•BST-2049: DeviceType only has readonly and no access field

•BST-2057: No support for multiple device states

•BST-2060 – There is currently no support for custom elements & attributes in device types. All issues around conformity of device types are being investigated for a future release.

•GRD & GPI – There is currently no support for GRD & GPI messages within the DDK. As the use of these messages is not now encouraged for new development, the plan is to provide minimal passthrough support for these messages for drivers that still need to interact with legacy systems that use them.