What’s New in UniPlot 5.9.3

This page describes the changes made to UniPlot 5.9.3 since version 5.9.2.


  • New Command File=>Export Data to convert NC files into other formats. Choose File=>More File-Functions=>Export (Convert NC data files)… to execute the command.
  • New command Edit=>Insert Table Of Contents. Right click on the document tab and choose Create/Update TOC to insert a Table of Contents to the active document.
  • All UniPlot-DLLs and EXE files have a digital signature “Uniplot Software GmbH”.
  • The public domain SQL database sqlite 3 shell is now included (sqlite3.exe).

New UniScript Functions

  New Functions in UniPlot 5.9.3
DocInsertToc DocInsertToc inserts or updates a Table of Contents.
NC_ExportData NC_ExportData converts UniPlot data files (.nc, .nc2) into another data format.
isfinite isfinite determines whether the given number is finite.

Modified UniScript Functions

The changes are listed in the history table at the end of the function description.

  Modified Functions in UniPlot 5.9.3
ST_seti The ST_seti function takes an vector argument (A) and removes duplicate elements. The function returns an index vector of the result.
finite finite checks if the argument is 0/0 or 1/0.
inf inf returns the result of 1/0.
isinf isinf checks if its argument is in the range -INF … INF.
nan nan (Not a Number) returns the number 0/0.

Bug Fixes

The following bugs have been fixed:

  • (ID1336): Most of the DLLs and EXE files did not contain the correct version numbers. The version number can be displayed in the explorer (Properties).

  • (ID1777): Table Object: If the line color or edge line was modified at the right or lower side of table object a memory access violation could occur that would be displayed when the document was closed (Error code C00000005).

  • (ID1926): auto_GetFileNameDialog: The dialog box was sometimes not initialized correctly.

  • (ID1929): Compressor map: The surge line and choke limit was sometimes swapped.

  • (ID1930): During the import of Excel 2007 xlsx files UniPlot sometimes crashed. The import filter contained an error which occurred irregularly.

  • (ID1932): The dialog box to edit the $-placeholders did not display elements containing an @-character.

  • (ID1934): Data=>Linear Interpolation: (Datasets=>2D Interpol Sum/Diff…) The standard deviation was not updated during data exchange.

  • (ID1935): auto_ReplaceTextDialog: The function displayed identical $-placeholders as often as they occurred in the page.

  • (ID1936): Datasets with more than 10,000 points did not display data symbols.

  • (ID1941): File=>Open: An IPW document could be opened by different instances of UniPlot simultaneously (Bug in 5.9.0, 5.9.1 and 5.9.2).

  • (ID1949): DocGetAllPages: The function could cause a memory access violation if a new page was added to an existing document.

  • (ID1951): The Edit=>Replace command would display the message “1 Text replaced”, even if no text was replaced.

  • (ID1955): fwrite(fp, ssText) modified the argument ssText unintentionally.

  • (ID1956): DdeInitiate failed, if the application was not completely started. Now DdeInitiate waits a moment (0.5 seconds) for the application to respond.

  • (ID1958): TYSetMinAndDelta: The function only set the parameters, if the dataset was already added to a document.

  • (ID1959): The command File=>More File Functions=>Waterfall-Single Cycle Import will now display an error message, if the data contains invalid values.

  • (ID1961) Formula-Interpreter: If a channel name and a used formula function name were identical, the function could not be created. Example:

    bit1 = bit(bit, 3)
  • (ID1962): Diagram Grid Lines: Dashes lines were plotted by accident with a function that would paint the gaps in white. The gaps were to small.

  • (ID1963) 2D-Dataset: In some cases the vertical hatch filling was not displayed.

  • (ID1964) XYGetData: If the dataset was a threshold line (XY_THRESHOLD_XCONST or XY_THRESHOLD_YCONST) XYGetData return 0 and 1 for the variable value. Now the function returns the axis limits. The problem occurred if two threshold values were used as a hatch fill area (Data=>Datasets=>2D Fill).