Released on October 28, 2022

Major change: Ribbon component migrated

The component which handles the menus has been migrated to a new component supported by DevExpress.

So far, we used a component named Elegant.UI for the menus but this component lacked support and is not supposed to be migrated to the new .NET plaform (.NET 6)

.NET 6 which comes from .NET Core is the new open source .NET platform written by Microsoft and QDV will be fully migrated to this platform in 2023 to ensure the sustainability of the product.

So we had to remove and replace all components for which the publisher cannot guarantee the migration. Today we need to migrate only one component: the Gantt diagram and we're working on it.

The new Ribbon made by DEV Express may display little graphical differences but the experience should be similar and closer to the latest version of the Microsoft Office suite.

Fix: Missing data in macros Context parameter

QDV macros have the Context parameter with the information about the current execution context, which includes the current selections in UI. Some of the values were not set:

•Context.CallingContextPlanner

•Context.CallingContextOverhead

•Context.CallingContextReportGenerator

New: Improved method IMinute.GetFieldsValues in the user API

The method IMinute.GetFieldsValues(firstRow, lastRow, …) returns the field values for the specified rows. If the user wanted to get all minute rows, he had to call IMinute.GetRowsCount and pass this value in lastRow parameter. This is no longer necessary. The firstRow parameter now accepts value -1, which means that all rows will be retrieved. This may be good for performance in complex macros in large estimates, where GetRowsCount could be quite slow.

Bug fix: Transparent background was not applied when loading WBS columns layout

The layout and formatting of WBS columns can be saved and loaded in .clb files. If a saved WBS column had transparent background – No Color, then when the layout was loaded from the file, the transparency was not applied to the column.

Bug fix: Management Module – Last backup date setting

Last backup date setting performed was not automatically saved in the management module. This resulted in backup each time the file was closed. Fixed now

Bug Fix: Cannot write “0” to a free text column in the WBS

A few years ago, we introduced types for WBS columns (TEXT, NUMERIC or ANY). Prior to this, all columns were untyped (ANY), so when you attempted to write a “0” value it was considered as a null value for all type of columns. Which was not correct because if was impossible to differentiate null and 0 in ANY, NUMERIC or TEXT columns. This was fine for ANY and NUMERIC columns but a TEXT column should make the difference and store either “0” or “”. This is now what a TEXT column does.