If you enabled the DIAdem 10.1 path behavior in the Compatibility dialog box and then changed the library path, DIAdem then changed the user path accordingly.
When recognizing target channels DIAdem now includes replacement signs for groups and channels. Refer to Name Conventions in the DIAdem help for more information.
The Val function did not convert a string with the NoValue value to NULL.
The DesktopChanged variable now also checks whether the bar definition was changed with the BarManager.
When DIAdem launched with the parameter /S some system files were not transferred. Therefore the program interface displayed at various places question marks instead of the correct symbols.
In the units catalog, decimal places were added to conversion factors that are dependent on the number Pi. Thus the conversion is more accurate.
When DIAdem deleted a channel group, DIAdem sometimes defined a different channel group as the default group.
When a channel was moved, the ChannelGroup property might still have referred to the original channel group.
If DIAdem edited a file with the DataFileHeaderAccess method and deleted a custom property with the RootPropDel method, this custom property still existed later.
If the Open in Explorer context menu was used in the file browser, files could not be opened in the Explorer if a path, for example, contained a comma.
The LoadQuery method of the NAVIGATOR script interface did not display an error message if an error occurred.
In the DataFinder Server Edition and in DIAdem encrypted DataPlugins could not be exported.
If the date/time values were imported in milliseconds in the ASCII Import filter and both second digits had the value 0, it could happen that the date was set to 1/1/0000.
The selective storage of DIAdem DAT files was incorrect if the minimum and the maximum of the channel were the same, and the channel also contained NoValues. In this case DIAdem saved the channel as an implicit channel and all NoValues were lost.
If a Band cursor was played to the end and then was restarted, the distance between the two cursor lines changed.
The display of a 3D model resulted in a shift if a normalization of the channel values was executed with different value ranges of the channels.
If a section of a curve that did not contain values was selected with a Frame cursor, it could happen that not all points were included when flags were set for this section.
A 3D model display was mirrored. A button has been included with which you can specify the rotational direction of the coordinate system.
A curve was sometimes incorrectly displayed if parts of the curve were at the edge of a clipping range.
Using non-existent enumeration terms in the VIEW script interface did not produce an error message.
The attempt to delete sheets with a non-existing index, could lead to a crash.
If channel names were entered manually in the 2D Axis System - Display dialog box, DIAdem did not display these channels before the display was refreshed.
The use of the script interface in DIAdem VIEW could lead to a crash not only to an error message if a parameter was not set.
If only the font was changed in a textbox, DIAdem did not retain the change after the dialog box closed.
If a display dialog box was cancelled, DIAdem sometimes did not display the worksheet before the next refresh.
If values were added or appended to a table, the last row of the block end could not have a value greater than the maximum channel length plus 10 values.
In the dialog box for configuring the rainflow results, the labels LCC and RPC were swapped.
The MatExtremeValues command returned the values-1E300 or 1E300 if the matrix only contained NoValues.
The contour calculation is faster now for data sets that contain many y-values that are identical to the y-maximum or to the y-minimum. The calculation can now also be terminated.
In DIAdem Version 11.1 and later versions, DIAdem no longer inserts a value with the same magnitude but the opposite sign, for the first reversal point of a load-time function, in Rainflow Classification. This behavior deviates from the stipulations of the brochure FVA 0/14, paragraph 1.2.4.
The type of amplitude calculation (FFTAmplType) was not recorded when a order analysis in the frequency range was executed in the recording mode.
In some cases, the optional index channel (FFTIndexChn) was not generated completely in the calculation of several FFTs.
If the data in the 3D displays Surface and Characteristic Diagram was triplet data, a wrong error message was sometimes displayed.
In the Calculator it sometimes happened that text assignments which contained a colon were incorrectly recorded, depending on the selected recording mode.
The FFC and NIC calculation is different to DIAdem 11.0 and earlier versions. DIAdem now uses the cumulative calculation of all peaks according to the EuroNCAP. You can use time at level for a continuous calculation within a peak.
When NoValues were replaced by a different value, the characteristic values of channels that were processed but did not contain NoValues were also changed.
The x-channels of the bottom and the top envelope curve were incorrectly named if the y-input channel contained NoValues.
After an incorrect evaluation of an expression in the Calculator, no further expression could be evaluated.
The THIV calculation might have returned incorrect results.
If an error occurred in a compound classification, DIAdem did not delete the already generated result channels.
The PHD calculation sometimes returned incorrect results.
In 2D-axis systems with mirrored x-axes and y-axes the scaling would change to linear, if the x-axes texts were selected in the layout and deleted with <Del>.
Now you can use the PicPalCtrlHSL variable to specify boundary colors in the global palette.
Empty channels sometimes occurred in curve transformations.
The setting Align subaxis ticks to grid sometimes returned different results when the layout was refreshed.
If the data layer or the graphics layer was disabled a configuration dialog box then opened and this dialog box was then cancelled, DIAdem enabled the data layer or the graphics layer.
Inserting an Excel table into a text object via the clipboard could lead to a crash.
Using the keyboard combination <CTRL+S> to save a report did not function if the target path contained a & character.
If a frame with a shadow was used in a report, the printout and the PDF export was incorrect.
Using the PicPDFExport command to append pages could lead to previously exported pages missing in the PDF document.
The tooltips of variables did not function if the value to be displayed contained XML code.
Opening DIAdem SCRIPT is now faster.
If a vector only contained NoValues when the ArraysToChannels command was used, DIAdem generated a numeric channels with zeros. Now DIAdem generates NoValuesinstead.
The ChnAreaInsert0 command did not function if there was a gap between the channel end and the position where the value was to be inserted.
If the MsgType parameter of the MsgBoxDisp command had the value MsgTypeError, DIAdem did not terminate this script.
The ArraytoChannels command does not support the VT_Decimal data type, which, for example, is provided by ORACLE data bases.
AUT scripts did not generate result channels automatically.
The GraphObjChnClear command only deleted curves but not constants.
An error occurred when a property was generated and filled with a name that contained invalid characters, for example, a digit at the beginning. Invalid characters are now replaced by an underscore.
If you used the GraphSheetMove command to move worksheets and then used the PicPDFExport command to print all worksheets to a PDF file, the alignment of the worksheets was sometimes wrong.
If the display of recent files was disabled in Windows, the SUD Editor sometimes crashed.
The ChnConvertToUnitSet command did not correctly convert the unit of channels that existed multiple times in the channel list.
In the Debug mode the tooltip of a variable did not appear until the cursor moved away from the selection and then moved back over the selection.
Sound output led to memory leaks.
In the Script DAC driver only the first digit of the linear specification of the format was evaluated if the UDI function Parse was used for a format specification.
If the time zone on the client computer was set without summer time and the automatic adjustment to summer time was enabled, the connected OPC server was sometimes declared not accessible.
If the filename for data to be saved contained a leading blank, the measured data could then not be loaded again. Blanks are now trimmed, like in Windows Explorer.
In the storage block dialog box a calculation could not be executed if the number of values for the storage cycle was entered as a variable.
If the Val function was used in formula blocks, an error occurred when the measurement started.
An error sometimes occurred when the variables for the GFSNIDAQ output blocks were written or read.
In measurements with SCXI modules and DAQmx, error messages sometimes occurred during the measurement preparation because the SCXI channels were not assigned to the correct DAQ tasks.
The correct configuration of the dialog box for the selection of an OPC server did not always lead to the correct connection with the respective OPC server.
The script driver now also supports scripts that are in the network.
ATFX files with "external components" are now supported better.
If you saved a TDMS file on a computer and then loaded the file onto a computer with a different summertime setting, a time offset could occur.
It sometimes happened in the ASAM data service that, if you used a laptop that was connected to a second monitor and you displayed a dialog box on the second monitor, that the dialog box could no longer display once the second monitor was disconnected.
The DIAdem AOP3 DataPlugin for ASAM ODS now also supports Santorin 3.4 Server from the company AVL LIST GMBH.
In the AOP3 DataPlugin the automatic recognition of the server version sometimes resulted in an incorrect search behavior for version 3.2 servers.
If the <> operator was used for text attributes in the ASAM data service, this search condition was ignored by the AOP plugin.