7.24.1150 |
  
|
7.24.1150 |
|
Released on July 2, 2024
A new overload of InterfaceQDV.Qdv.Initialize was added which allows for setting the UI language by external clients. The signature is
Initialize(silentMode As Boolean, licenseCode As String, uiLanguage As String)
While the clients run mostly in a silent mode, the UI language is still important. For example, the language of the exceptions, the headings of native columns in WBS or Minutes workbooks, field names, and other messages provided by the API are using the UI language. So, the processed workbooks and other data are affected by this setting. You can now use the new uiLanguage parameter to set the UI language.
When editing a workbook in Excel or importing a workbook from Excel in Overhead, in row workbook of Minutes, WBS, Article or Set database, not supported charts sheets (a separate sheet that contains only a chart) are now deleted as they are not supported by QDV and caused subsequent errors when selecting these sheets in QDV.
When editing a workbook in Excel in Converter, not supported charts sheets (a separate sheet that contains only a chart) are now hidden as they are not supported by QDV and caused subsequent errors when selecting these sheets in QDV.
QDV could report an AccessViolationException error randomly during the work with the application.
When running Load default report or Save report for Overhead report more times, there could be an error message displayed.
Undo works again for set input fields now also in user mode, it has been working only in edit mode so far.
When searching for invalid data like text in numeric columns there was error message ‘no such table: MinutesSearch’.
When new Article or Set database was created, it was localized only to current QDV language. User would need to localize it to other languages in Field manager. Now new article and set databases are localized to all QDV languages so when you open the new database in another QDV language, it displays native column names in current QDV language, not the QDV language the database was created in.
Instead of an error dialog and incomplete report, the report is now completed and there is now warning message "Invalid formula '{0}'. Report header cell for column '{1}' cannot be set.".
Estimate Minutes and Nomenclatures fields are now localized to all languages instead of only to current QDV language when opening an estimate. The difference for user is that when user opens Multilanguage editor in Fields manager, the user can see the localized value for each QDV language instead of only the languages the estimate was opened in so far.
A button has been added in PartnerApplication -> Spigao -> Create SPIGAO Sheet. This button initializes a sheet named "SPIGAO_JSON".
When a user clicks on "Import From Spigao" or "Import Local Spigao Project", a JSON file is imported into the "SPIGAO_JSON" sheet of the environment workbook.
Printer errors sometimes happen due to printer setup in Windows, not in QDV. These printer errors can still happen, but they are now better handled in Printer settings dialog in QDV to inform the user appropriately about such system printer errors.
QDV Spreadsheet didn’t allow R<number> or C<number> as Defined Names created in Automation – Manage Names – New Name dialog like in Excel, however it allowed names like R<number>_abc which worked properly in QDV, however e.g. ‘Edit in Excel’ function for such Overhead workbook failed as these names aren’t valid in Excel so we also don’t allow Defined Names starting with R<number> or C<number> anymore in QDV.