|
|
 |
UniPlot's Bug List
Last Update: July 2010
If you find an error please submit the Bug-Report.
Thank You!
(ID28) UniScript: The LibMain function cannot invoke the loadiclib
function.
(ID366) If a Windows Meta File (.wmf) is inserted into a UniPlot
document (for example a logo), the document page cannnot be displayed
correctly if embedded into a Word or PowerPoint document (or other program).
Work around: Convert the logo to a high resolution PNG file (for example
600 dpi resolution).
(ID526) COMBI files created with the new system cannot be converted.
(ID548) A data filter cannot be specified in Tools=>Options=>2D-Dataset.
(ID555) UniScript-Debugger: If UniScript is in debug mode you cannot
right click to set a new break point. Work around: Use the F9 to set
break points.
(ID1082) If a diagram displayes only a small area of a contour plot with
color filling a WMF file cannot be created correctly. The color filling gets
lost. Workaround: Create an EMF file.
See Fixed Bugs in UniPlot 5.14.x.
See Fixed Bugs in UniPlot 5.13.0.
(ID2013): The Window menu was sometimes not properly updated. Specifically,
the Window menu failed to add new documents to the list.
(ID2217): DialogBox: If a dialog box contained a symbol combo box and
used callback functions (for example for push buttons). UniPlot would crash if
the callback function was invoked.
(ID2218): The channel attribute C_format of netCDF files was not
evaluated correctly for hex or integer formats. For exxample the format
C_format = 0x%08x formats a decimal value 1000 as 0x00001001. For MDF files
(INCA) an empty channel attribute C_format will be written to the NC file.
If needed, the format string can be set in the data browser.
(ID2228): 2D-Curves: If an axis was log scaled the data point symbols were
missing. This bug was in all versions since version 5.10.1.
(ID2195): 2D-Dataset with Hatch Fill: A close curve could cause a memory
access violation. If one of the axes was log scaled, the hatch fill was not
displayed.
(ID2196): Edit Embedded IPW Pages: Some important commands were missing if
a UniPlot page embedded in another application was activated. For example the
data exchange command was not available. A new command Save Copy As has been
added to save a page as a IPW file.
(ID2198): UTX-Filter: During the removal of empty columns on the right side
of the data matrix an error could occur. The problem only occurred under UniPlot
5.11.0.
(ID2204): Data Exchange: The same file name was sometimes displayed for
all data sources in the Data=>Data Exchange (Page) dialog box.
(ID2206): MATLAB Import: UniPlot could crash during a mat-file import.
(ID2161) The XYZGetNumberOfPoints function was documented but missing.
(ID2168): 3D-Dataset-Interpolation: The Thin-Plate-Spline interpolation
failed for some datasets. The interpolation has been modified as following: If
the interpolations fails a linear interpolation is executed and a warning is
displayed in the event window. See also: Data=>Interpolation.
(ID2169): IFILE: A reading sometimes occurred if the file contained Indicom
extension data. See also Import of IFILE Data Files.
(ID2170): poly_triangulate: The function could not be invoked with three
data points. At least 4 data points were needed.
(ID2171): Formula Interpreter: The following functions returned column
vectors instead of a row vector: smooth, fft_filter, derivative, integral, max,
min. Column and row vectors cannot be mixed in an expression using one of the
following opeartors: +, - , *. /.
See also Formula Interpreter 1 - Introduction.
(ID2173): UTX-Filter: Empty columns on the right side of the data matrix
will be ignored.
(ID2181): UTX-Export: Each attribute was separated by two newline separators.
Now, only one separator is used.
(ID2183): Objects with string arrays were displayed incorrectly, for example
print [. a = ["Hello1", "Hello2"], b = 123];.
(ID2184): MATLAB files withe 0-Bytes strings in cell arrays could not be
read.
(ID2185): Formula Interpreter: The replace_missings() function did
not recognize the value 1e10 as a missing value.
(ID2188): In some cases a 2D curve could not be selected with the mouse. If
a curve was overlapped by another curve and clipping was enabled the curve
could not be selected.
(ID2189): Grid lines could not be displayed as a dotted line.
(ID2191): PDF-Export: The export used the default printer driver page size.
Example: If the printer driver of the PDF Export was set to A4, the page could
not be exported as A3.
(ID2192): Hatch filling of 2D-Datasets: If the curve was a closed polygon,
the number of data points was limited to 2047 points. If the curve contained more
points, a memory access violation occurred. This bug has been fixed as as follows:
The number of points is limited to 181072, otherwise the hatch filling is not
displayed. This limitation does not apply to monotone increasing datasets.
(ID2127) UTX-Impot-Filter and Excel-Import: The import failed for Excel files
in the biff 2 format (Excel 2.1 files). This bug only occured in UniPlot 5.10.2.
(ID2137): XYZFilterCallback: The new 3D filter function introduced
with UniPlot 5.10.2 failed with a runtime error, if one channel contained only
missing_values or constant values for X or Y. The error occured during data
exchange as well.
(ID2138): If the registration of UniPlot in the Windows registry failed
(uniplot.exe /regserver), no error message was displayed.
(ID2141): ExcelRead and all other Excel read functions did not handle
shared formulas correctly. The function returned an empty string instead of the
formula result string.
(ID2142): The UniScript-COM-Server usserv.exe did not display message boxes.
(ID2151): 3D-Map: If the X-, Y- or Z-values of the original data was out of
the range -1e5 to 1e5 the data was removed. The reduce3d function removed
all data points in this range instead of the range smallter than -1e10 and
greater or equal +1e10 as documented. This error only occured in UniPlot 5.10.2.
(ID2078): Data Import: The Import function in UniPlot 5.10.x contained a bug.
While checking if a data file was a MATLAB file, the file was opened but not
closed again. If an Excel file was imported, the file could not be accessed with
Excel while UniPlot was running.
(ID2085): matlab_load: MAT files with 3, 5, 7,..-dimension arrays
could not be read.
(ID2088): matlab_load: MAT files with array of structures could
not be read.
(ID2090): In UniPlot-5.10.x some country specific resource DLLs were
missing. Therefore UniPlot would display some messages in English.
(ID2111): Data exchange of 3D datasets: The fill color between the isolines
could get lost if the standard autoscale function was selected. This bug
only occured in UniPlot 5.10.1.
(ID2114): XYCopy: The function did not copy the scaling settings
correctly (offset and factor). This could bug occured in the data
magnifying function.
(ID2109): The ifft function did contain a bug if the function was
invoked with a matrix instead of a vector. Example:
f = fft([1,2,3;4,5,6]'); ifft(f).
(ID2115): The fspline function had an error. For some data the function
ended up in an infinite loop.
(ID2116): A UniPlot page embedded in a document, e. g. PowerPoint
could not be edited correctly (OLE). While closing UniPlot, UniPlot crashed
and would not be finished correctly.
(ID2118): 3D bars:: Bars in a 3D diagram that were clipped at z-max were
not filled with the correct color. The bar was filled with the color
that color that correspnded the the z-max value.
(ID2119): If matlab_load was invoked with a Non MATLAB file, the file
was opened but not closed.
(ID2067): Enviroment variable UNIPLOT_INI: If the enviroment variable
UNIPLOT_INI was specified UniPlot 5.10.0 displayed an Internal error and
did not start. See UniPlot's Use of the Windows Registry.
(ID2070): matlab_load: UniPlot crashed if the matlab file contained
empty elements, e.g. a cell array with the dimention 0-by-0.
(ID954): fgetline() could not read UNICODE files. The function can read
UNICODE files if the file contains a BOM (byte order mark). The file must be
opened with (see fopen) in text mode.
(ID1969): ASAM-ODS Browser (RPC) Because of a bug, UniPlot
could not access the ASAM-ODS data base of AVL-Puma Version 1.4.
(ID1984): XYSetData and TYSetData: The functions could not set
data with only one data point. The error occured in the data exchange function.
(ID1985): Data=>Data Exchange (Document), Data=>Data Exchange (Page):
Before the data is exchanged, all datasets are set to 0-points. The
"Ignore File" options has been corrected. The option caused an error if
selected for the first data file. Another error occured if
the first data file did not contain any channels needed for the data exchange.
(ID1987): ASAM-ODS Browser (CORBA) The first data base access failed
because the password was not set correctly. After the error message the login
dialog was displayed. This bug has been fixed.
(ID1988): Diagram=>X/Y/Z-Axis=>Parameters: Sometimes the delta value
was not displayed with enough decimal places. Example:
Start value = 500, End value = 505, Delta = 0.5. The delta value was displayed
as the value 1 (rounded to 0 decimal places). Now the value 0.50 will be
displayed.
(ID1990): The multi channel import did not save the data source information.
The function did not handle missing values and did not handle record filters. See
File=>More File Functions=>Waterfall-Multi Channel Import.
(ID1994): In UniScript the font size had to be specified as a negative number.
Now all font sizes are converted to negative numbers automatically.
(ID2016): 3D-Dataset: If all data points of a 3D-dataset were lying on the
data hull, the hull was not closed if the "Entire Hull" option was selected.
(ID2017): IsFileText() always returned FALSE (0) for UNICODE-files
(utf-16, utf-16-le).
(ID2018): Text-Editor: The editor did not load UNICODE files.
(ID2019): Text-Editor: During loading of text files the display flickered.
(ID2020): Text-Editor: Long lines of text were wrapped, even if wrapping
was switched off.
(ID2025): FileToField could not handle UNICODE files. Now the function
can read UNICODE files containing a BOM (byte order mark).
(ID2026): Sometimes the text_file_write() function did not write the BOM
(byte order mark) correctly.
(ID2034): Dialog Box=>Data Filter: The values in the dialog box
were not initialized with the specified value if the value was out of range of
the corresponding channel. Example: rpm > 2000 AND rpm < 10000. The value
10000 was replaced with an empty string if the data range of rpm was smaller
than 10000.
(ID1336): Most of the DLL's 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 occured 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 occured 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): Diagramm 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 vetical 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 occured if two threshold values were used as a hatch fill area
(Data=>Datasets=>2D Fill).
(ID1917): Using Windows 2000 the import of Excel data files failed.
(ID1918): The GetDirectoryWriteAccess and GetFileWriteAccess
sometimes returned an incorrect return value.
(ID1919): The CORBA-DLL's for ASAM-ODS with CORBA-Interface did not work
on machines missing the DLL msvcr90.dll. This bug only occured in UniPlot 5.9.1.
A msvcr90.dll is no longer neccessary to load the CORBA-DLL.
(ID1925) The modified flag was not set if a page was removed from a
document. If the document was closed without another modification, the document
was closed without asking if the user would like to save the modified document.
(ID1928) If a bitmap was inserted from clipboard into a document page
and right afterward a different document page was activated the bitmap got
lost. This error occured only in UniPlot 5.9 und 5.9.1.
(ID1907): The Data=>Reload Data menu command did not work.
(ID1911): Some DLL's were not installed by the UniPlot 5.9 setup program.
The ASAM-ODS browser could not be used without the missing DLL's.
The error did not occur if UniPlot 5.9 was installed as the update to an
existing UniPlot installation.
(ID1912): The Edit=>Search and Replace (IPW) command failed with an
error message, if the IPW file contained a table object but no text objects.
(ID1827): Map Dataset: Sometimes color filling and isolines did
not match. This error occured if the values of the interpolation matrix
and the isolines were identical. The error occured frequently if the
matrix contained integer numbers.
(ID1828): A table object could not be moved using the arrow keys.
(ID1834): The Data Browser: The browser could not display files with
more than approx. 5 million rows. Now it is possible to display files
with multi-million points. Limit for netCDF-up files: 2 billion points per
channel.
(ID1835): The number of data points of a netCDF-up file was limited
to approx. 260,000,000 points. Now this limit is 2 billion points
(see also Application Limits).
(ID1836): The marker output of 2D datasets can be very slow for large
datasets. Therefore markers are only displayed if the number of
displayed markers / Marker-Frequency < 10000.
(ID1839): Windows-Vista: Display error in the status bar.
(ID1842) UniScript error in UniPlot 5.8.2: "/" characters were not
allowed in a "define" statement. Example: #define TEST "a/b".
(ID1843) Small display error with diagrams: Sometimes the position of the
grid lines and the axes tics did not match. The offset was 1 pixel due to a
rounding error. The error can still occur in some cases.
(ID1851): AppHelp() did not work with 2 parameters. The help file
opened but the topic did not open. Example: AppHelp("sin", GetRootDirectory() + "help/up-en.chm")
(ID1852): The File=>Close (Save Compact) command could lead to data loss.
If the command was used for a new document and the "Cancel" button was pressed
in the SaveAs dialog, the file was closed without saving.
(ID1873): Addin 3D Classification of a XYZ-Dataset: The values
were written into the file without decimal places (Format %8.1g).
Now 5 significant digits are saved (%10.5g) or the user can set the number
of decimal places.
(ID1867): ExcelGetSheetNames sometimes did not return sheet names
for large Excel files. Only the first sheet could be accessed.
(ID1890): excel_sheet_put_rows only worked with 2 parameters.
(ID1807): File=>File Quick View: If the File Quick View template contained
only one diagram, the 2D dataset y-channel name and the 3D dataset z-channel name
were used as the page name.
(ID1808): Data=>Data Exchange (Document), Data=>Data Exchange (Page):
If multiple sheets from one Excel file were used in a document, all sheets were
immediately replaced. A message box will now appear after the first sheet is
selected with the question if all sheets should be replaced.
(ID1809): UTX-Import-Filter: If a data file contained more than one text
channel with an identical name, the import failed. See
UniPlot Data File Format Specification.
(ID1810): IFile Import: If the data file contained channels with only
one data point, the import failed. This error occurred only in UniPlot 5.8.1.
(ID1811): IFile Import: The following features have been added to the
IFile Filter: Import of up to 99 operating parameters, long channel names (more
than 10 characters), import of calculated channels (these features have been
added to the IFile format with IndiCom 1.3).
(ID1813): UniScript: "//" comments could cause problems in
#define commands. This bug has been fixed.
Example:
#define ABC 123 // Comment
#define DEF 456 /* OK */
sprintf("%d", ABC) // Bug in uniplot 5.8.1, OK in 5.8.2
sprintf("%d", DEF) // OK
(ID1815): Autocale Axes: If all coordinates of a datasets were negative, the
automatic scaling failed.
(ID1816): IFile Import: Sometimes, if the NC file was saved in the
netcdf-up format, not all channels could be imported. See Tools=>More Options,
"Data Import and Data Browser=>netCDF Filetype".
(ID1818): auto_GetFileNameDialog: New option to sort the file names. The
names can be sorted in alphabetical order or by date (recent files at the top).
(ID1821): fft: The FFT calculation of datasets with more than 5000 data
points was very slow if the number of points was a prime number (for example
99991 points). Now the number of points will be extended by padding to a
product of small prime numbers.
(ID1824): Error bars: The Error bars could only be displayed with a dashed
line style.
(ID1801): The documentation of GetSaveFileName() did not contain the
form <ssFilename, nFilter> = GetSaveFileName(...).
(ID1802): Images (jpg, bmp, ...) were inserted incorrectly into a UniPlot
document page if the DPI value (dots per inch) was missing in the file. The image
was plotted distorted.
(ID1803): Edit=>Clear: It was possible to delete the background layer.
If a page does not contain a background layer the paste function caused a
memory access violation. This error occurred only in UniPlot 5.8.0.
(ID1804): LayerDestroy: The LayerDestroy function could delete
the background layer. A page must contain a background layer. Now the
function returns FALSE (0) if a background layer is given and the layer will not
be deleted.
(ID1805): Diagram=>Align Drawing Objects: Elements could not aligned to
top edge.
(ID1769): Online-Help: The table of contents was incorrect. This bug
was only in UniPlot 5.7.0.
(ID1770): "Text: Create Header Table": If an attribute contained a very
long string, the data table created was much wider than the paper size. Now
these cells will be broken into multiple lines.
(ID1775): NC-Browser: The combo box for the second Z-channel
in the NC-Browser was not supported.
(ID1776): The column with of a table was not calculated correctly, if
the cell format was set to display numbers but the cell contained an invalid number.
(ID1788): The Undo function did not undo the names of text objects correctly.
(ID1790): Then OBJRemoveMap(hObj, ssName) function removed a map
from an object and marked all other maps of that object as deleted.
(ID1792): Closing a document would sometimes cause a memory access
violation. This bug was caused by an internal error.
(ID380): UniPlot:3DView): The number of data points for the
scatter plot was not limited. This could lead to a program crash if the
number of points was greater than approx. 5000 points. Now, only the first
5000 points will be displayed. The number of points for the 3D-curve has also
been limited to 1000 points.
(ID1726): XYFind: The function did not return the data point with the
index 1, if the data was sorted in decreasing order.
(ID1731): LayerSetAxisTitle, LayerGetAxisTitle: The newline character
has been changed from \r\n to \n to make the functions compatible with
text objects (TBGetText) and table objects (TableGetText).
(ID1732) regex, regsplit: The functions did not handle Unicode
characters correctly and did not support the case-insensitive flag.
(ID1733): Data=>Dataset List: New buttons have been added to
modify the dataset order in a diagram: "One Up", "One Down", "Send To Back",
"Bring To Front".
(ID1735): An error occured, if a text file was opened with SynEdCreate()
and then opened again with EdCreate().
(ID1736): The case of a file name of an existing text file was
modified, if the name was specified with a differnet case. For example the call
SynEdCreate("TEST.TXT") would change the case of an existing file
with the name "test.txt" to upper case.
(ID1739): The interpol and auto_xy_RemoveDoublePoints function
did not handle datasets with only one data point correctly.
(ID1748): Data=>Data Exchange (Document), Data=>Data Exchange (Page):
The option "Use Record Filter specified in Datasets (Curve)" was not used
correctly for 3D-Datasets.
(ID1749): Data=>Interpolation: The option
"Interpolation-Range-Automatically" has been added to the interpolation dialog
box.
(ID1750): UTX-Import-Filter: UTX formatted Excel files could not
be read if the header contained empty rows between the key words UXX-BEGIN
and \t(UXX-END). This error occured only in UniPlot 5.6.3.
See UniPlot Data File Format Specification.
(ID1751): FileToField, StringToField: If an Unicode character with
a value greater than 255 and a byte value of the lower byte matching the
value of the separator (59 for ;) was not handled correctly. This bug
could occur during the import of UTX-Excel files.
(ID1752): UTX-Import-Filter: UTX formatted Excel files could not be read if
a cell contained a semicolon. See UniPlot Data File Format Specification.
(ID1753): Map Calculator: The INCA format string
CALIBRATION VALUES V1.0;,; was incorrect, if the decimal symbol in the
Regional Options was set to ".".
(ID1755): If the option "Do not keep history of recently opened documents"
in the Group Policy Editor (Gpedit.MSC) was enabled, UniPlot terminated with a
memory access violation during startup.
(ID1758): TableDeleteColumn: If the column index was greater than or
equal to the last column, a memory access violation occured. For example, the
call TableDeleteColumn(hTable, 1000) did not remove the last column.
(ID1678): The DocAddPage function failed if the page was located in a
different document. The function could be used if the page was newly created
with the PageCreate function.
(ID1677): The DocInsertPage could not be used because of a bug in the
function.
(ID1681): PDF-Export: If the path name contained a percent sign
the function DocPrintPDF and PDF-Export failed.
(ID1682): The rspline filter function failed for non-monotone 2D
datasets.
(ID1685): In the print preview (File=>Print Preview), the displayed page
sometimes flickered rapidly and a memory access violation could occur.
This bug occured only in UniPlot 5.6.0 and 5.6.1. This bug was partly fixed in
UniPlot 5.6.2 (ID1662).
(ID1692): The Label Data Points field function for 2D-datasets
was incorrect. If the configuration was modified by a right mouse click on
one of the labels and then selecting the Edit Label command the function did not
work correctly if the dataset contained more than 50 data points. The function
created a label for each data point and slowed down UniPlot significantly.
(ID1694): Data=>Data Exchange (Page) The group name of MDF files
(e.g. INCA) was not handled correctly if the group name was removed
in the new data files. The function has been modified to remove the group
name from all channel names. This simplifies the channel selection.
(ID1700): 2D-Datasets were not removed from the memory when the document
was closed. This bug was in all versions since 5.3.1
(ID1703): 2D-Datasets: Datasets with non monoton x-coordinates
could not be edited using the Edit Y coordinate button.
See Data=>Edit 2D-Dataset Coordinates.
(ID1704): File=>More File Functions=>Synchronize Time Data (Files)
The channel attributes add_offset and scale_factor for time channels
were partly not evaluated. Example: If a time channel was measured in
milli seconds and the scale_factor was set to 0.001, the offset calculation
and data preview was correct. but in the calculation that followed when the
OK button was pressed the scale_factor was ignored.
(ID1705): For 1 point datasets the Line Style Hatch Style and
Fill Color button were deactivated. Now they are activated and can be used.
ID(1656): If the standard printer could not be accessed, UniPlot started very slowly.
(ID1658): The File=>More File Functions=>Excel-Report: Create New Report Template)
command could not be used, because of a missing function. See Report Templates.
(ID1662): In the print preview (File=>Print Preview) the displayed page sometime flickered rapidly
and a memory access violation could occur. This bug occured only in UniPlot 5.6.0 and 5.6.1.
(ID1664): ExcelRead could not read cells with Umlauten (ä,ü,ö,ß) correctly.
This error occured only in UniPlot 5.6.1.
(ID1431): If a file was selected using the File=>Open dialog box and
the file was not an IPW file, the file was loaded into an editor.
A "file cannot be opened" message box now appears.
(ID1469): XYIsTYDataset: For datasets with 0 data points, the function
always returned the value TRUE (1) even for XY-datasets.
(ID1562): fspline: The function returned the value 0 if the y-coordinates
were constant (y = constant). (The bug was fixed in 5.6.0, but wasn't added to
the bug list).
(ID1574): ASAM-ODS (RPC): If a submatrix contained 0 records, the function
to merge the submatrices failed.
(ID1575): If a page was removed from a saved UniPlot document (*.ipw), the
modified flag was not set.
(ID1577): Sometimes datasets and their maps were not removed
from the IPW file when the document was closed.
(ID1584): Excel-Import: The sheet name was not added to the origin attribute
in the netCDF file. Without the sheet name, users had difficulties with the
data exchange function. Example: d:\test.xls [sheet1].
(ID1601): Diagram: Drawing objects were not moved correctly with the diagram
when the arrow keys were held down.
(ID1613): ExcelRead: The function did not return Unicode strings.
For formulas with a string result, the function returned an empty string.
(Example: =Sheet!A1). This bug occured as well in the File=>Import Data
command when an Excel file was seleceted.
(ID1614): Datasource could not be edited. For example, the datasources
to calculate a difference map could not be renamed when the page name was
changed. The dialog box can be accessed via the dataset context menu.
Right click on a dataset and select Edit Function Parameters....
See Data=>Edit Function List.
(ID1634): TCM-Import-filter: The TCM-Filter addin library was not compiled
correctly. If the addin was loaded, the bug caused problems with the
File=>Import Data command.
(ID1641): NC-Browser: Add DataFiles: This function had a bug which occured
if two files contained string channels and a different number of channels
A waring was added to the event viewer:
"Grid Add Data", "Channels have different data types, Name xxx".
(ID1642): If more than one MDF file was open simultaneously, a memory
access violation occured. This bug occured only in UniPlot 5.6.0 if a netCDF
file was open in the data browser and a second file was imported using the
File=>Import Data command.
(ID1644): UTX-Filter: The channel name was missing in the
NC attibute long_name, if the norm name addin was used and the scheme name
did not exist in the norm name catalog.
(ID1645): If a isoline label was removed from a XYZ dataset
using the Toolbar=>Data, the isoline was plotted over the isoline labels.
This bug has been fixed.
(ID290): The status bar could only display the first 127 characters of a
string.
(ID1413): The "Check Formula Channels" command did not work correctly
if the option "Do not overwrite imported channels with formula channels"
was selected (see Tools=>Formula Configuration).
(ID1444): MDF data files with more than 100 time groups could not be
imported. In UniPlot 5.6 this limit is set to 1000. Older UniPlot versions will
fail to open NC files with more than 100 time groups.
(ID1494): The FileToField did not work correctly if a cell started with
a double quotes (") but did not end with a double quotes.
(ID1495): The sorti function failed to sort a row string vector.
(ID1502): The "Check Formula Channels" command did not work correctly
if alternative formulas exist. (see Formula Interpreter 1 - Introduction).
(ID1512): ExcelWrite() could cause a memory access violation if the
matrix had more than 100000 text elements. This bug occured in all UniPlot 5.x
versions.
(ID1513): If the table object text dialog box was closed using the "Cancel"
button a memory access violation could occur if the auto_ReplaceText()
function was invoked before the dialog box was opened.
(ID1514): During the import of Excel files using the
auto_GetFileNameDialog dialog box the sheet name dialog box was displayed.
(ID1515): The "Delete Formula" command in the Tools=>Formulalist dialog
box did not work, if formulas were selected which name started with the
same character.
(ID1519): The data cursor line style could only be set if both cursors
were displayed. (Data=>Data Cursor Configuration)
(ID1520): The documentation of UniPlot command line option /IniFileName was
incorrect. The parameter name and the file name are separated by a space
and not by an equal sign (=). See UniPlot's Use of the Windows Registry.
Example:
uniplot.exe /IniFileName "d:\uniplot.ini"
(ID1524): The XYZGetInterpolZValues returned incorrect values if
the linear interpolation method was set and a data point outside the convex
data hull was given. The bug occured randomly.
(ID1527): The Data=>Data Cursor=>Move Datasets documentation was
missing.
(ID1529): An error could occur if a netCDF file was opened with the
data browser that was already opened by another user.
(see File=>Import Data). This bug is in all versions since UniPlot 5.3.2.
(ID1530): Rainflow-Addin: The histogram did not handle "half cycles"
correctly.
(ID1532): Because of bugs in some Window Versions (see
http://support.microsoft.com/kb/286360/en) the Windows-API function
GetEffectiveRightsFromAcl() sometimes failed. This bug caused problems in
GetFileWriteAccess() and GetDirectoryWriteAccess() functions.
If this bug occurs a message will be displayed in the UniPlot Event Viewer and
the two functions will always return TRUE.
(ID1539): auto_ImportData: The function could not evaluate
the sheetname in square brackets behind the Excel file name. Example: // Sheet "a" import failed.
ssNCName = auto_ImportData("d:/test.xls[a]")
(ID1543): The File=>Import Options dialog box had an error.
The option "Calculate formulas during data file import" was disabled
when the dialog was closed using the OK button.
(ID1546) Print Preview: In the Print Preview function the field functions
and global placeholders are not updated.
(ID1547): auto_LoadDataset: If a style file was not loaded
using the auto_LoadStyleFile function UniPlot used the currently loaded
style file. Because a style can contain filter functions and scaling values
(offset/factor), it was possible that data curves were modified unexpectedly.
In UniPlot 5.6.0 the current style file is unloaded. If a style file
is needed it must be loaded using auto_LoadStyleFile. When the automation
is finished, the original style file is reloaded.
(ID1550): If the field function @f{legend} was used without a specific
diagram name, a legend was not displayed if the text object was copied to
the background layer. Now an error message is displayed:
Invalid Legend - no Diagram Name.
(ID1553): XYZGetIsoline: The isoline value index assigned correctly.
(ID1155): As of UniPlot 5.5.0 the UTX import filter is used to
import Excel and Text files. Due to this change the treatment of invalid
channel names has changed. Spaces were replaced by underscores. This could
cause problems during data exchange function. Now all spaces are removed and
only special characters are replaced by underscores.
(ID1557) IFile: The intake manifold pressure correction method ("nultyp" = 4)
will be executed for the "nultyp" = 257 as well.
(ID1560) The simplify filter function (Douglas-Peucker algorithm) was incorrect.
The \t nTolerance parameter has been corrected.
nTolerance: Specified the maximum distance between the original curve and the
simplified curve. A value of 1 sets a tolerance of 10%. The values 2,3,4,5, etc.
always divide the tolerance by 2. Therfore a value of 4 is a tolerance of 1.25%.
A value of 30 sets a tolerance of almost 0% Default value is 5.
(see Data=>1D and 2D Dataset or Filter Functions for XY datasets).
(ID1487) File=>Import Options: The newline character in the
placeholder text for the axis title was not converted correctly.
(ID1488) CSV-Filter: The revised import filter in UniPlot 5.5.0 did not
handle text columns in CSV and Excel files correctly.
(ID1489) MDF-Filter: Due to a error in UniPlot 5.5.0 MDF files could not
be imported.
(ID1412): If the 2D-Dataset dialog was closed using the ESC key sometimes
the datasets on the page were not displayed. Only a replot (ALT+R) would fix
the problem.
(ID1435): The File=>Close (Save Compact) command did not save the file's
creation date. The new function SetFileTime fixes this problem.
(ID1436) @{legendfile}: The function changed the display order of the
data files.
(ID1447): The CopyFile and MoveFile can now be used
with Unicode file names.
(ID1456): The fgetline() function in UniPlot 5.4.1 did handled
0 characters differently from older UniPlot versions. 0 characters were treated
als new line characters. Now the function will read to a "real" new line
character, but only return the string ending at the first 0 character.
(ID1458): If the command Set to Default was used in the
Tools=>Options dialog box the sector size was set to 512 Bytes. Now the
sector size will be set to 4096 Bytes. Only when running under Windows NT 4.0 is
the sector size set to 512 Bytes.
(ID1464): IFILE: If the maximum resolution of an IFILE was 0.025 degree
crank angle UniPlot calculated a Crank Angle (CA) channel with a incorrect
resolution. The resolution was 2 times higher than specified.
(ID1462): 2D Dataset: If a 2D dataset contained NANs (Not a Number)
UniPlot got stuck in an infinite loop.
(ID1466): ExcelRead(): If the Excel file was created by a Far East Excel
version and the number of string was quite high the Excel file could not
be read.
(ID1468): FileToField(): If the column separator occured in quotes
and the parameter bQuotedNumberConversion was set to TRUE (1) the file could not
be read.
(ID1471): Data=>Data Exchange (Page): If a record filter was specified
for a NC file and a channel contained only missing_values, a script error
occured (DS_interface_SetDataSource.ic, row 523).
(ID277) UniPlot would sometimes start without displaying a window if
an IPW file was double-clicked in Explorer, and
an UniScript function would display a message box during startup.
This bug had been fixed in UniPlot 4.2.1 but found its way back into
the program due to a new library.
(ID1345): 2D-Datasets: Sometimes a dataset could not be selected with the
mouse. This error occurred mainly with datasets containing less than 512
data points.
(ID1347): Polar Plot: Curves in polar plot could not be selected with
the mouse.
(ID1353): Data=>Data Exchange (Page): The option "Auto Scale all Axes"
had no effect. The styles in the 2D-Style dialog box were sometimes displayed
incorrectly.
(ID1365): StringToField could not be invoked with a single
return parameter if the input string contained text elements.
Example: The following call would create a exception:
ret = StringToField("1.0\tTest\t3.0", "\t");
This bug occured in all UniPlot 5.x versions.
(ID1366): Data Import: If elements in text data file contained
characters with a code greater than 127 (e.g. ü, ö, ä) the characters
were incorrectly converted. This led to incorrect attribute values in netCDF
files. This bug occured in all UniPlot 5.x versions.
(ID1368): PageSetBackgroundPageName: It was possible for a page to use
itself as a background page or it was possible to use a page that already had
a background page. This caused an error. In both cases the function will now
return 0.
(ID1374): The tic() function returned an incorrect value.
(ID1375): Diadem Import Filter: The scale_factor and add_offset
channel attributes were missing.
(ID1381): The strOemToChar function was incorrect in all UniPlot 5.x
versions (Unicode bug).
(ID1387): Time Axes: Date/time values smaller than 1 created an error,
e.g a time value 12:00 o'clock is saved as 0.5.
(ID1388): UTX-Filter: Spaces before the attribute name were not ignored.
The attribute value was truncated by the number of spaces.
(ID1389): Data=>Data Exchange (Page): The dataset list displayed an
incorrect NC file name. The first NC file name was displayed for all datasets.
(ID1391): obj_save(): If the object contained strings with 0 characters
or invalid characters like 0x01 or 0x02, the created file was invalid. The files
could not be read with obj_load().
(ID1392): UniPlot 5.4.0 can be used with NT 4.0 again. The latest service
pack (Service Pack 6.a) and Internet Explorer 6 must be
installed. We do not test UniPlot 5.x with Windows NT 4.0 any longer. Therefore
UniPlot may contain bugs that do not occur with Windows 2000/XP/Vista.
(ID1393): EPS Export: If the printer driver would write
"Printer Job Language (PJL)" commands the EPS export did not work.
(ID1394): PagePrint: After a call of the PagePrint function, the
document title displayed in the windows title was truncated after 32 characters.
This bug occured in the EPS and PDF Export.
(ID1396) Data=>3D-Dataset=>Z-Values: If the isoline vales where
specified as -0.8,0.1,0.8 the value 0.0 was calculated as -1.38778e-16 and
added to the list of values.
(ID1397): If a netCDF data file was opened with nc_open and then
accessed with nc_create, the call did not fail. This would lead to a memory
access violation. This bug only occured in version 5.3.2 and 5.3.4.
(ID1402): fgetline: If the lines of a text file were separated by a
single "\r" character (older Macintosh files), "\r" would not be identified as a
line separator.
(ID1407): DialogBox, AppSetBatchMode: If UniPlot was in batch mode,
a dialog box containing an OK callback function was still displayed. Normally
all dialog boxes and message boxes are suppressed in batch mode.
(ID1410): Seldomly, nc_varput() would write incorrect values for
byte- and short channels. This bug occured in UniPlot 5.3.2 the first time.
(ID1411): GetWindowsVersion did not return the minor version number.
The function returned the same version for Windows 2000 to Windows
Server 2003 (see documentation).
(ID1414): If UniPlot is using an INI file instead of the Windows registry
to save program settings (command line key /IniFileName or enviroment variable
UniPlot_Ini), a memory access violation would occur if UniPlot tried to read
a string longer than 4096 characters.
(ID1418): The F1 key to open the online help did not work in dialog boxes
created with the DialogBox function.
(ID1239): ASAM-ODS Browser (CORBA) is using the new
OmniOrb 4.1-Library (see http://omniorb.sourceforge.net/).
(ID1303): Mouse wheel zoom: The zoom factor range have been extended to 1%
to 1600%. (Zoom: Hold down the Ctrl-key and spin the mouse wheel).
(ID1316): The Event_Error function caused a memory-access-violation if
the message text contained the string "2%.nc" or other similar strings
(e. g. Event_Error("a", "2%.nc")).
(ID1318): ASAM-ODS3-Browser (ASAM-ODS Browser (RPC)): The
Calculate formulas during data file import option was not evaluated correctly.
See File=>Import Options and Tools=>Formula Configuration.
(ID1322): XYZCreate: The function could not be invoked with three
parameters.
(ID1325): Data Exchange: The
Use Record Filter specified in Datasets (Curve) option did not work.
(ID1326): If the text of a text object was not clipped at the object frame
and the object was moved with the mouse, the page was not updated correctly.
(ID1327): NC-Browser: Editing an attribute value sometimes failed if
the attribute data type was float. Example: The attribute add_offset
could not be set to 1.1 if the NC file was created from a UTX file.
(ID1309): UniPlot Files: This update corrects a bug recently found in version 5.3.2.
Files created with UniPlot 5.3.2 containing datasets with filtered data could not
be displayed correctly with older UniPlot 5 versions. The datasets were invisible.
UniPlot 5.3.2 files can be opened with UniPlot 5.3.3 without any problems. When saved
UniPlot 5.3.3 will correct the bug. These corrected files can be opened with all
UniPlot 5-versions.
(ID1246): A number of errors in the Undo/Redo function have been fixed. Some
of these errors could crash UniPlot.
(ID1250): ncgen.exe: UniPlot could crash if a warning occured. The
string length of global attributes was limited to 512 characters.
(ID1253): Grafic-Export: If the target directory was write protected, the
export failed without an error message.
(ID1254): Data-Cursor: Some bugs have been fixed:
The cursor could not be moved if the cursor was located on the left or right
diagram border.
A cursor could not be displayed if the diagram contained
3D datasets.
The cursor could not be displayed if the data was sorted
in descending order. The cursor could only be used if the x-data was strictly
monoton increasing.
(ID1257): An incorrect errror message could be displayed if a netCDF function
failed (Unicode problem).
(ID1259): The nc_varcopy function failed if the the NC files had
different byte order.
(ID1262): Because of a bug in the UniPlot netcdf interface, the
reading and writing of NC files in the original byte order could be very slow.
(ID1263): Grafic-Export: If the temp directory contained more than
16000 files the export of png, emf, jpg etc. files failed.
(ID1271): 2D datasets: If the curve was drawn with a dashed line style
sometimes the last dash was missing.
(ID1283): 2D datasets: If data symbols were plotted on the diagram border
the symbol was partly clipped. Now if the data point is inside or on the diagram
border the symbol will not be clipped. The symbol clipping can be enabled using
the registry key "Settings\data-symbol-clipping".
(see UniPlot's Use of the Windows Registry).
(ID1284): 3D datasets: The Thin-Plate-Spline interpolation could fail if
the input data was distributed extremely evenly.
(ID1232): Data Exchange: If an IPW document contained references to nc files
that did not exist in the specified location the channel selection could not
be modified even if the invalid nc-files were replaced with valid files.
(ID1233): Data Exchange: If a dataset in a page was calculated from 2 or
more datasets (for example a dataset created with Datasets=>Create Region
function), an index out of range error occured.
(ID1235): auto_GetData and other functions to load data failed
if the group name was stripped from the channel name of MDF files.
(ID1237): GetFileWriteAccess and GetDirectoryWriteAccess: For some
computers the functions returned the value 0 (no write access) even if
write access was granted.
(ID1154): WMF-Export: For some diagram layouts diagrams and datasets were
missing in the WMF file.
(ID1156) GetSaveFileName: The file name extension was not
automatically added to the file name.
(ID1157): Text Object: The text box extent was calculated incorrectly
for very short text (1,2 or 3 characters).
(ID1163): The TableGetPenList function caused a memory access violation.
(ID1165): PDF-Export: If the PDF file name contained blank characters,
the PDF file could not be created.
(ID1166): The CnLoad() function needed write access if the file was
created with UniPlot 3.x. A second mistake was that those files were not closed.
after loading.
(ID1167): The obj_save() and obj_load() function had a number
of errors when objects contained strings with NULL characters.
(ID1168): NC-Browser: If the channels were displayed in rows,
frozen channels were replaced by other channels. This bug
occured if the dialog box was resized using the ">>" button.
(ID1169): NC-Browser: If the channels were displayed in rows,
global attributes could not be copied into the clipboard.
(ID1170): Asam-Browser: The formula channels were not updater or created.
(ID1171): The ExcelWrite function converts negative numbers of type "I"
to a positive number in the range 0 to 65535. Negative numbers can not be
used for this data type. The documentation did not mention this limitation.
(ID1173): File Quick View: If a template with a stacked diagram
was used, data was added to the grid diagram.
(ID1175): IPW-Save: The file name extension .ipw was not
automatically added to the file name. See File=>Save As.
(ID1178): PageGetBoundingRect: Hidden axes elements were not ignored.
Therefore the bounding rectangle could be greater than expected. For example,
this bug could occured in the PowerPoint export.
(ID1179): The TBGetAlignHorz and TBGetAlignVert returned wrong
values.
(ID1180): The font dialog box displayed fonts where names
started with an @ character. For example: "@Arial Unicode MS". Text objects
using this font could not be printed correctly.
(ID1185): XML_SetUserData(hParser, data): If data
was a UniScript object (see obj_create), a memory access violation
could occur after the function was invoked 32 times.
(ID1190): PageUndoStart: If the description text was longer than
approx. 60 characters, a memory violation error could occur and UniPlot
would exit.
(ID1191): The fwrite_int8, fwrite_uint8 functions were incorrect if
the BIG_ENDIAN_BYTEORDER was used (see fopen).
(ID1193): fread: If the parameter n was greater than the number
of elements in the file, the function failed. Now all elements will be
returned.
(ID1194): Some users could not use the
File=>More File Functions=>Save document pages as a PDF file
command if they had Ghostscript properly installed. In UniPlot 5.2.0
the Ghostscript-exe file was used. Now the Ghostscript-DLL is used.
(ID1202): UniPlot:3DView (up3dv.exe) would not start on some computers.
(ID1213): A number of bugs in the documentation of the following functions
have been fixed:
XYCreate, XYAddData, XYSetData,
TYCreate, TYAddData, TYSetData.
(ID1218):RegOpen failed for elements in the registry
where the user had only read access rights because UniPlot tried to open the key
with read and write access. Now these keys will be opened with read access only.
(ID1219): ExcelRead() could not read cells that contained
far east characters (for example jananese characters). For these cells
UniPlot returned an empty string. This bug created some problems in the
Excel data import.
(ID1220): PageGetBoundingRect ignored the bounding rectangle of the
background page. See Page=>Select Background Page.
(ID1222): Text objects containing alias field functions, e.g. _a(Title), were
only updated in the active page. See File=>Edit Alias Table.
(ID1223): Saving the data of a 2D-Datensset in an Excel file failed
if the dataset contained more than approx. 8300 points
(Error message "Index out of range").
(ID1225): Line Object: If diagram coordinates for a line object were selected
and the axis scaling was changed, the line coordinates were updated to new
coordinates. The line object did not change its position.
(ID0173): The documentation for the Browser=>Create New NC File
command was missing.
(ID0743): Akima spline: The function to calculate the akima spline did not
compute the last data point correctly. Sometimes the last point was a huge
negative number. This bug has been fixed.
(ID1107): IFILE: If the file contained one or more channel with 0-length the
following incorrect error message was displayed: "IFiles with multiple resolutions
are not supported in this version". Now the file will be created. All channels
with 0-length will be skipped.
(ID1111): The output of the nonlin function into the command window
was incorrect due to a Unicode problem in versions 5.0.0 to 5.1.2.
(ID1112): ncgen.exe, ncdump.exe and up3dv.exe
did not start on computers where Microsoft C-Runtime-DLLs (msvcrtd.dll) (Debug)
were missing. This error occured only in UniPlot 5.1.0 to 5.1.2.
(ID1119): The DialogBox function did not initalize the radio buttons
correctly.
(ID1121): The auto_GetFileNameDialog created an error if the
specified directory did not contain any data files.
(ID1122): Undo function: The dataset Name, Info text and legend text
was removed if the undo function was executed. This was a bug in
all UniPlot 5 versions.
(ID1124): UTX-Filter: Channel attributes were not handled correctly if
the attributes values were empty or contained numbers but not text.
(ID1026): Table Object: For hight zoom factors the column with and row height
could not be modified using the mouse.
(ID1127): Table Object: Global document placeholders were not updated
it the cell name contained a placeholder value. The result was that the text
could not be changed because the field function would reset the text to the
old value.
(ID1130): If NC_Edit() was invoked during start up some of the commands
e.g. Copy would not work.
(ID1131): Formula Interpreter: If a formula name was identical to
a global attribute of the NC file, the depending channels were not updated.
Now the global attribute will be ignored. The Help button in the
Tools=>Formulalist did not open the correct help topic. The button
"Remove Formula" did not remove a formula if the corresponding ic File did
not exist. A new command has been added to the context menu of the NC browser
to remove all formula channels from an NC file.
(ID1135): Data Browser: If the freeze command was selected for
an already frozen channel an error occured.
(ID1136): Program Editor: The "save As" command failed without an error
message if the directory was write protected. The window title displayed the
new location even if the file was not saved.
(ID1142) Debugger: If a UniScript file name contained more than one
period, e.g.. Test.1.1.2006.ic the file could not be debugged.
(ID1145): Grafic Export: The save directory could not be set using the Browse
button.
(ID1151): ASAM-ODS-3-Configuration: The Save directory for NC files
could not be set using the Browse button.
(ID1097): The uninstall program did not remove all installed files.
(ID1099): The File=>Print Preview command could cause UniPlot to crash.
This bug was in UniPlot 5.1.0 and 5.1.1.
(ID1100): The close button in Print Preview would close UniPlot
and remove toolbars (UniPlot 4.2.x to 5.1.1).
(ID1101): Table Object: If a table cell contained more than one
place holder (text enclosed in Dollar characters) a script error could occur.
The bug has been fixed. Now only the first place holder in a cell will be
evaluated, all the other place holders will be ignored. Only one place holder
should be inserted into a cell.
(ID1102): If a doument page contained field functions the
File=>Print Preview command could crash UniPlot (UniPlot 4.2.x to 5.1.1).
(ID1104): ASAM-ODS4-Browser: To avoid duplicate attribute names the name
will be extended by the base name, for example "AoTest_id". Only the first 8
characters of a text channel have been saved in the NC file. This bug has been
fixed.
(ID401): The Edit=>Find In Files command could not search for text that
contained a "|" or "@" character.
(ID875): An IPW document could be opened by more than one UniPlot instance
at the same time. This could lead to crash of UniPlot. This bug has been fixed in
UniPlot 4.2.4. Because of the new Libray used in UniPlot 5.1.0 the bug was
added to UniPlot.
(ID1090): DialogBox: If the number of elements in a ReportControl
was reduced the report was not updated correctly. For example this bug occured
in the dialog box Data=>Dataset List when the checkbox
"List only datasets of the selected diagram" was marked.
(ID1091) In 5.0.0 and 5.1.0 multiple diagrams could only be selected
by clicking inside the diagram area. In 5.1.1 the diagram can again be selected
by clicking on the diagram title of label (while the Shift-key is pressed).
(ID1092) auto_GetFileNameDialog: The function failed to list
the file names if a file name contained a @ character.
(ID1093) @f{labeldataset}: The field function calculated the
label position incorrectly if the XY dataset did not contain any
filter functions.
(ID1094) Formula Interpreter: The check formula command did not work
correctly if the formula name and the formula result channel name was not
identical. The function also failed for formulas of the form "A=A" or
"A=B" and "B=A".
(ID1064): Zoom: The upper left corner of a document page could only be
accessed when in full page mode.
(ID1065): 3D-Dataset: If the option "In a Box" and "Fit to Gradinent" was
selected for isoline labels, the box was not completely visible.
(ID1066): NC-Browser: If the column width in a data grid was wider than the
default width, the selected column was occasionally not moved into the view.
(ID1067) Registry: In version 5 UniPlot, uses the registry key "UniPlot5" to
avoid conflicts with UniPlot 4. By accident some settings (i.e. the toolbar
settings, the recent file list or the settings of the NC Browser) were still
written to the key "UniPlot".
(ID1069) Table-Object: If a number format was set for an empty cell, the value
0.0 was displayed in the cell.
(ID1071) ASAM-ODS-Browser 4: If the ASAM structure contains elements of type
AoSubTest, the structure could not be displayed.
(ID1072) XYZCreate: Non square matrices could not be processed. When checking
the rows (rvY) and columns (rvX), x and y were mismatched.
(ID1073) 1D-, 2D-, 3D-Datasets: During data exhanges, the info text and the
legend text were not updated. They still displayed the old data data source and
channel names. XYZCopyConfig(hSrc, hDest, bCopyMap)
If bCopyMap is FALSE (0), the legend text and the info text is not copied.
(ID1079) The f|EdGetSelectedText| function for the Text-Editor and the
Rich-Text-Editor returned only the first character. This bug only occured in
UniPlot 5.0.0.
(ID1080) If an error message contained a percent sign (%), the error
message was displayed incorrectly.
Example:
def test()
{
a = "Hello";
MessageBoxInfo("Test %s", a[1], a[2])
}
(ID1084): DT_Format does not format values smaller than 2 correctly
if "%c" is specified. This bug is caused by an error in msvcrt80.dll.
It will be fixed in one of the next updates.
(ID1085) Excel-Sheet names, containing an @ character were not displayed
the the sheet selection dialog box.
(ID1086) poly_is_point_in_polygon() returned incorrect results.
A list of known bugs in UniPlot 4.x can be found here:
Bugs in UniPlot 4.x
Copyright © 1996-2010
Uniplot Software GmbH, Germany.
| |
|
