|
|
 |
UniPlot's 4.x Bug List
Last Update: September 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.
(ID1100): The close button in Print Preview would close UniPlot
and remove toolbars (UniPlot 4.2.x to 5.1.1).
(ID1102): If a doument page contained field functions the
File=>Print Preview command could crash UniPlot (UniPlot 4.2.x to 5.1.1).
(ID1044): The commands File=>Close (Save Compact) and
File=>Save As saved the file with 512 bytes per sector, even if the
source file was saved with 4096 bytes per sector. That could cause problems
if the file contained a high number of datasets (e.g. > 800)
(see also Tools=>Options).
(ID1045): The auto_xyz_SetIsolineStyle functions had an error.
(ID1046): The ObjCopy function did not copy the object name of text
objects.
(ID1048): The commands File=>Close (Save Compact) and
File=>Save As could be very slow if the document contained a huge number
of pages and/or datasets. The performance has been improved.
(ID1049): The modified flag for document pages was sometimes set incorrectly.
Due to this problem the save command was sometimes slow.
(ID993): NC files: The ignore case option could only be set for a single nc
file. The function has been modified so that the flag can be set globally: nc_set_option(ncid, "nocase", 1);
// For all NC files (ncid = -1)
nc_set_option(-1, "nocase", 1);
(ID998): Online Help: The function help index was not listed in the correct
sort order.
(ID1000): An error object could not be added to a UniScript object. o = [.]; o.e = error_create("test", 1, "message");
(ID1016): Sometimes the wait cursor did not change to an arrow cursor.
(ID1027): If a string matrix contained NULL characters the string was
truncated at the first 0-Byte character:
Example: sm = ["a\x0b", ""]; sm[1;1] != "a\x0b";.
(ID1028): The print output of a real matrix into the command window could not
be canceled with the ESC key, example: print rand(10000,1).
(ID1032): The DialogBox function had multiple errors (UniPlot 4.2.4 to
4.2.6).
(ID1037): 3D Dataset: If the option "Fit to Gradient" for the isoline labels
was set, the gradient was not recalculated if the diagram size or scaling changed.
(ID882): poly_triangulate had two errors. 1.) For certain distributed
data the function caused a memory access violation, for example
poly_triangulate([0,0,1,1],[0,1,0,1]). 2.) The error handling
was different than described in the documentation. In case of an error
the function returns a string vector with two elements. The first element
is the error id and the second element the error text.
(This bug was incorrectly marked as fixed in UniPlot 4.2.4)
(ID900): The AppQuit() function had an error. UniPlot goes into an
infinite loop when the function is invoked and UniPlot hangs.
(ID902): Debug-Tooltip: If the cursor was placed while debugging on a
real variable with exactly 40 rows and 1 column, the debugger would hang and
cause an endless loop.
(ID903): Load 3D-Hull: If the third column was invalid the command failed
without an error message. In UniPlot 4.2.5 an error message will be displayed
and all values will be set to "m".
(ID917): The obj_save function did not save variant matrices with strings
correctly. Example: In the following code
o = [.a = [1, "2"]]; o.save("c:/test.xml") string "2" was not saved in
the file.
(ID964): ltostr created an incorrect result string for negative values
for base 10.
(ID966): NC-Brower: If the channel attribute C_format = "" was empty an empty
field was displayed. UniPlot 4.2.5 will display the value in the default format
if the string is empty (see File=>Import Options)).
(ID974): Error in documentation of fwrite: The data type "real48" can
only be read (see fread) and not written.
(ID986): A memory access violation could occur if huge matrices were assigned
to a variable:
Example:
a = zeros(1,1e6) // Works!
a = zeros(1,1e8) // Does not work. a will be destroyed.
The next access to a would create a memory violation.
(ID991): Data Exchange: If a channel contained only invalid values
(missing_value) the data exchange was aborted. In UniPlot 4.2.5 the data of 1D and
2D datasets is set to 0;0 and the data exchange is continued. For 3D datasets
the data exchage will be aborted.
(ID992): MDF-Format: If the channel name in the MDF file was not
null-terminated parts of the following channel comment would be added to the
channel name. This bug occured if the channel name in the MDF file was
32 characters long.
(ID995): smMat = ExcelRead(): To convert real numbers, the format sting
"%g" was used. In UniPlot 4.2.5 the format string %.16g is used. Otherwise
the OLE date/time values were converted incorrectly. If ExcelRead
returned a date/time string the return value was, for example, 38500 instead
of 38500.423.
(ID996): o = error_create("a",1,"b") was treated incorrectly by the
garbage collector. The strings in o were deleted but the object was still
valid.
(ID852): Data-Browser: Insert data from clipboard failed if the clipboard
contained more than 1000 data points.
(ID853): Excel-Report: If a page break was inside a data header, the last
data row was not copied to the next page and the last row at the end of the
table was missing.
(ID860): Data-Browser: While the Browser was active, UniPlot was checking
if another UniPlot instance was accessing the NC file. This check was done
while Windows was idle. The CPU activity was high with up to 99% busy.
The function has been changed, using a timer to avoid this problem.
(ID863): The mem_set function did not accept a string as the third
parameter, e.g. a = mem_alloc(10); mem_set(a, 1, "Hello", "char").
(ID867): Formula-Interpreter: If a formula was already existing in
the NC file, the attributes were not updates, for example the attribute units.
(ID868): Stacked Diagram: If a diagram was moved using the mouse, the drawing
objects connected to the diagram did not update their position. If multiple
diagrams were movedm, a memory access violation occured.
(ID869): Data-Browser: Sometimes a comma was displayed as the decimal sign.
(ID870): Help-System: If UniPlot is installed on a server and the
Microsoft Security Updates from June 2005 is installed the UniPlot help system
does not display the help text. See the following article on the Internet
for more information:: http://support.microsoft.com/kb/896054/DE/. To solve
the problem add the following key to the registry on your local computer: \\HKEY_LOCAL_MACHINE
\SOFTWARE\Microsoft\HTMLHelp\1.x\ItssRestrictions
Create the key MaxAllowedZone with the value 1 (use regedit.exe to create
the key).
(ID874): NC_GetVarNames: The parameter bOnlyRealChannels was not
evaluated.
(ID875): An IPW file could be opened simultaneously by two or more
UniPlot instances. This could cause a program crash.
(ID882): poly_triangulate had two errors. 1.) For certain distributed
data the function caused a memory access violation, for example
poly_triangulate([0,0,1,1],[0,1,0,1]). 2.) The error handling
was different than discribed in the documentation. In case of an error
the function returns a string vector with two elements. The first element
is the error id and the second element the error text.
(ID883): 3D-Dataset: The magic number 999,999 in the cell A1 or in the
upper left corner of a text file was not recognized correctly.
See File=>More File Functions=>Load 3D Data Matrix.
(ID884): Akimaspline: If the data was linear the spline would swing between
the linear points.
(ID885); DocShow: The DocShow function only hid (SW_HIDE)
a document if the document contained at least one page.
(ID887): UniScript-Debugger: Sometimes tooltips values for variables were
not displayed.
(ID889): Addin rs_auto: The combo box to select the style was missing in
the dialog box to select the data files.
(ID890): 2D-Dataset: Filter functions could not assigned to a dataset
if the dataset was not added to a diagram. For the same reason
the XYCopy function failed, if the dataset contained filter functions.
(ID891): Difference Map: During the data source exchange difference maps
were not updated.
(ID892): Data-Browser: UniPlot would crash if a variable of the data type
NC_CHAR with only one dimension (single character) was edited.
(ID894): OLE2: If a UniPlot document page containing 2D datasets was actived
in-place in a MS-Word document it could not be modified. UniPlot would sometimes
crash if the active element was deactivated. If the embedded UniPlot page was
opened in UniPlot (OLE 1), the error did not occur.
(ID819): Print Preview: The update of the field functions were missing.
(ID843): Some properties for the bar style of 2D datasets were missing
(ID844): 2d-Dataset: The data scaling (x-Offset, etc.) was not updated
correctly when the data was exchanged.
(ID845): If the font heigth was specified as a positive value the subscript
and superscript text was not displayed correctly.
(ID846): If the iniatialize string of a multi select list or report
element in a dialog box was empty or did not contain a selection a memory
access violation occured (see DialogBox).
(ID810) auto_ReplaceTextFromNCFile: The netCDF file was not closed if
there was no text to replace.
(ID820) The function to empty the event window (see
View=>Event Window Configuration) did not delete the events correctly.
Sometimes after a new start of UniPlot events already deleted were displayed
in the event window.
(ID821) MDF/VS100/INCA: Certain MDF files that could be read with UniPlot
4.2.0 could not be imported with UniPlot 4.2.1. The bug has been fixed.
(ID822) Problem with local variables if objects were used.
Example: def test_local()
{
a = [.];
a.a1 = 1;
a.a2 = 2;
// ...
a.a299 = 299;
a.a300 = 300;
b = 1; // Error message
}
In the function above UniScript calculated an incorrect number of local variables.
The elements "a1" to "a300" were treated as local variables. That created the
following error message "To many local variables: *** internal error ***". In
fact the function has only two variables, a and b.
(ID824) Style File: If a style file in the old format (*.icb) was converted
to the new format (*.sty) the attribute "label-format" (3D-Style) was not saved
correctly. The created style file could not be loaded.
(ID825) MDF Files: The MDF filter has been extended to support the datatype
double. Time channels that are stored in the MDF file as 64-Bit-double values
cannot be read.
(ID826) Import: If the unit string is already enclosed in square brackets
in the source file, the brackets will be removed to avoid double brackets.
(ID827) Data exchange: In one of the older UniPlot versions an important
function call was removed for test purposes. The function call updated depended
datasets, for example the sort function.
(ID829) Function DialogBox: The number of parameters of the callback
functions were determined incorrectly. If the number of parameters
were greater than expected, the function was invoked with less parameters than
neccessary.
(ID831) UniScript-Parameter: Functions as parameters could not invoke
themselves. Example: def TTest()
{
AppSetTimer(TTest, 100);
}
This bug has been fixed.
(ID835) Axes scaling: If the x-axis has a descending scaling the axis title
could not be left or right aligned.
(ID837) The RegConnect function did not work in UniPlot 4.2.0 and 4.2.1.
All functions which accessed the Windows registry did not work as well.
(ID840) Excel-Report: If an excel template used the option
Scaling/Fit to in the "Page setup" dialog box the report could not be
created correctly. The option is now set to
Scaling/Adjust to 100% of normal size.
(ID277) Under certain circumstances, UniPlot would start without displaying
the main window. This error occured if an UniScript function displayed
a message box during startup or an ipw file in Explorer was double clicked
or by a DDE command.
(ID763) When a new UniPlot file was saved the file name was clipped after
8 characters. Example: UniPlot11 => Save As => UniPlot1.ipw instead of
UniPlot11.ipw
(ID764) When another page was added to a document after creating a page with
the Diagram=>Create U3D Diagram command, the U3D-Plot was no longer visible.
(ID770) The data source exchange did not work (see
Data=>Exchange Datasource for active Page) if the file name contained
blank characters. This error occured only in UniPlot 4.2.0.
(ID772) The MDF import filter had problems with data groups not containing
any channels (see Import of MDF Files).
(ID777) If the FileToField function was invoked with incorrect
parameters, a memory access violation occured.
(ID779) The Browser=>Check Formula command had some errors:
1.) Incorrect messages were added to the event window;
2.) The summary of missing channels in the log file did not display all
missing channels;
3.) OnFormulaFinishEval() were invoked at the wrong time;
4.) Every time the function was invoked, 3 maps were created but not destroyed
(see MapCreate).
(ID780) DialogBox: If one or more blank characters were inserted
between the name of a callback function and the closing OR sign, the callback
function was not invoked. Now blank characters are ignored.
(ID786) In text objects, the elements @t{nn} and @s{nn} could only evaluate
values in the range -10 bis 10.
(ID799) Caused by a build error, the DLL rs_pdsi.dll could not be
loaded (see RS_PDSI, Version 5.2.2).
(ID801) The style order file cannot be edited, if the directory
c:\program files\UniPlot\template is read only. The directory can be
set in the Tools=>More Options dialog box. If
c:\program files\UniPlot\template is read only, the style order files
(*.smp) should be copied into directory set in the Tools=>More Options dialog
box.
(ID334) The Save As Command in the editor always added the extension .ic.
If a file name with a different extension was typed in, e.g. test.txt the file
was saved as test.txt.ic. The function has been changed The extension will
only be added to the file name if no extension is given.
(ID653) The call sqlite_open("") caused a memory access violation.
(ID660) Scrolling problem: Using the scroll bars white lines were added to
the display.
(ID676) The Help button did not work in the Browser=>Interpolation
dialog box.
(ID686) Open Data Broser => Channel-Interpolation => Cancel => Data is
missing. Workaround: Reopen Browser.
(ID691) NC-Browser: Channels were missing if columns were moved and than
a new NC file was selected without closing the dialog box. The error occured
if the new NC file had less channels than the currently open NC file.
(ID702) UTX-Filter: If an Excel file in the UTX format contained new line
characters (ALT+ENTER) inside a cell, e.g in a channel name, the file could not be
imported correctly. Newline characters are now removed.
(ID707) Dataset copy: The datasets were copied to the clipboard in the
order they were selected. Now they are copied to clipboard in the order they are
displayed in the diagram. The same is valid for copying drawing objects to
clipboard.
(ID716) If a dataset was loaded from a file, in which the file name contains a
percent character ("%") the data exchange failed.
(ID718) Exchange Datasource: During the data exchange using the
Data=>Exchange Datasource for active Page function all placeholder
values which could not be found in the NC file were replaced by an empty string.
(ID720) Stacked Diagram: When a y-axis was added to a stacked diagram
the grid settings were set to default. Now the settings are set to default only
when the grid is created. The y division is set to 1 centimeter when the grid
is created.
(ID721) The user name could not be removed in Tools=>More Options.
(ID734) Akimaspline: The function used an invalid data point to calculate a
coeffizienten. The result was that all points between the second last and the
last original data point were set to 0. The error occured irregular.
(ID736) Error in Exchange Datasource (dx-Function). See
Insert Datasets into a Template. If a data source had more
than one option, the table created were incorrect.
To fix is insert the following line to \uniplot\script\dx-main.ic:
ssFile = sum(svPath[3:4]) + " {" + ssImportOptions + "}";
before (line 133)
ssImportOptions = strcat(ssImportOptions, ",");
This bug is fixed in 4.2.0.
(ID740) The input of "def test()" in the command window can cause a
memory violation error. The function is defined but invalid. Steps to create the
bug 1.) Type "def test()" and press enter 2.) type ";" 3.) function test() is
invoked => Crash. The bug has been fixed.
(ID748) Style file (Tools=>Dataset Style Configuration): Umlauts and
other special characters in style names are not handled correctly.
2. Error: If you create a style "abc" the name is displayed as 2D-abc='name'.
The name should have been displayed as name='2D-abc'. The bug does not occur if
at least one attribute is added, e.g bar='1'. 3. Error: Style file name is not
displayed (only 4.2.0 beta 1).
(ID641) The dotted line style could not be set for 3D datasets.
This bug was only in UniPlot 4.1.4.
(ID639) UniScript: The handling of the number of local variables was
incorrect. A UniScript function with 256 local variables could be compiled
but caused a a memory access violation when the function was executed. (The
number of local variables is limited to 255.)
(ID637) Pen width, style and color could not be set for a 3D dataset.
This error has been corrected.
(ID636) Printing Problem: If a document was printed on a printer other than
the default printer, all page elements were printed with an offset of some
millimeters. This has been corrected.
(ID624) In UniPlot versions 4.0.0 to 4.1.2 the number of 2D datasets is
limited to at least 800 datasets. This limit is valid for UniPlot 3.x as
well for all datasets with more than 1000 data points.
Under Windows 2000 or Windows XP this limitation can be removed by using a
different sector size for IPW files. The sector size can be set in the
Tools=>Options dialog box. If the sector size is 4096 byte, the number
of datasets is only limited by space on the hard drive. This setting will
be used when a new document is created.
IPW files with a sector size of 4096 bytes cannot be displayed or edited under
Windows 98 and Windows NT 4.0.
Under Windows 2000/XP the sector size of an IPW file can be changed using
the ipwtool.exe program.
Example:
To change the sector size to 4096 bytes open a command prompt and
type in the following command:
"c:\Program Files\UniPlot\Program\ipwtool.exe" convert -s 4096 *.ipw
To change the sector size to 512 bytes use the following command
(IPW files for Windows NT 4.0 and Windows 98 must have 512 bytes per sector)
"c:\Program Files\UniPlot\Program\ipwtool.exe" convert -s 512 *.ipw
Display the sector size (-i for info).
"c:\Program Files\UniPlot\Program\ipwtool.exe" convert -i *.ipw
ipwtool.exe cannot be used under Windows 98/NT 4.0 to change the
sector size.
The DocCreate and IsFileIPW have been modified to set and get the sector size.
(ID628) 3D-Dataset: UniPlot did not display the correct color for the
smallest isoline value in 3D datasets with enabled color gradient. UniPlot
always used the min color instead of the color specified for the
corresponding isoline value.
Example: Assume we have a map with z-coordinates in the range from 35 to
100. For this map we have specified the isoline values 10, 20, 30, 40 und
50 and the correspnding colors. UniPlot should dispaly the color specified
for the value 40 for all areas between 35 and 40, but instead UniiPlot used
the color specified for the min value. The bug has been fixed.
(ID626) Sometimes black dots were displayed in a map plot. This error
should not occur if a new map is created. If you open an IPW document and
find this error you can fix it as following:
Double-click an isoline to open the Data=>3D-Dataset dialog box.
Select all isoline values in the isoline list.
Click on the line style button.
Choose a valid value for line style color and line with and click OK.
(ID629) The commands 2D-Dataset=>2D-Spline and
2D-Dataset=>2D-Akima Spline which can be enabled using the
Tools=>Customize User Toolbar did not work under UniPlot 4.x. This bug has been fixed.
(ID617) If the solve function was invoked with incorrect parameters
UniPlot crashed.
(ID543) The help index for UniScript key words (if, else,
for, ...) did not direct to the right pages.
(ID537) The FEVIS-Import-Filter had a bug.
(ID532) Some MDF files (VS100 /INCA) could not be imported.
(ID533) If a variable type was changed in a for loop a memory access violation
occured. def test_for()
{
for (i in 1:1000) {
i = "a"
}
}
(ID535) The incorrect property dialog box was opened when the user right clicked
on an OLE object (e.g. Excel Sheet).
(ID553) Sometimes when a dataset was clicked a different dataset
was marked.
(ID558) The XYZGetIsoAreas() function caused a memory access violation
when no isolines were specified for a 3D dataset. The documentation for this
function was missing.
(ID571) The FS_GetFreeSpace() and FS_GetTotalSpace() function
returned valid values only for drives with a capacity of less than 2GB.
(ID588) UniScript: The obj_keys function had an error: obj = [.1,2,3]; obj_keys(obj, 0, 10) // did not work
obj = [.1,2,3]; obj.keys(0, 10) // Did work
(ID590) The obj_save function did not save Variant matrices and negative
keys correctly. o = [. 1 = [1, "1"]]
obj_save(o, "d:/test.xml") // => a[1] was missing in the file
o = [. -1 = 2] // negative Keys
obj_save(o, "d:/test.xml") // error
(ID591) During the deallocates (garbage collection) of a list object,
a memory access violation could occur.
list = [.];
t = list;
for (i in 1:100000) {
t.val = i;
t.next = [.];
t = t.next;
}
t = list = 0; gc();
(ID610) The documentation of the RemoveDirectory was missing.
Filter Funcitons for 2D datasets: If more than one filter function was
specified the second and all following filter functions used the original and not
the filtered data. This bug has been fixed.
XYGetData: The function call XYGetData(hData, 0) returned the value
0 and not as documented the original data. This bug has been fixed.
Channel Interpolation: Channels containing missing_values could not be
interpolated. This bug has been fixed.
Import, Load Dataset: If a dataset in a diagram was selected the load
function failed. This bug has been fixed.
Style Files: The isoline values, color and pens got lost during the
conversion of style files in the UniPlot 3.x format. This bug has been fixed.
2D Dataset Style: When a curve was selected the style in the toolbar combobox
would not be selected. This bug has been fixed.
GetDirectory did not return hidden files. This bug has been fixed.
GetDirectory is now a uniscript function. The source code can be found in the
script\object.ic file
Objects created with obj_create had a problem. Some expressions could
only be evaluated using helper variables: // o = obj_create()
// o.a = obj_create()
// o.a[1] = 123
o = obj_create()
o.a = obj_create()
temp = o.a
temp[1] = 123
// o = obj_create()
// o[1] = obj_create()
// o[1][1] = 123
o = obj_create()
o[1] = obj_create()
temp = o[1]
temp[1] = 123
This bug has been fixed. With UniPlot 4.1.1 even the forms marked as comments can
be used.
UniPlot setup program: The PDSI Ini file was overwritten. This bug has been
fixed.
If utf8_encode and utf8_decode were invoked with an empty string
(e.g. utf8_encode(strempty(1,1))) a memory access violation occured.
This bug has been fixed
The functions strCharToOem and strOemToChar were missing.
UniScript: If a function contains more than 255 varialbles UniScript caused
and access violation. In 4.1.1 an error message is displayed.
UniScript: UniScript files with more than 32700 lines of code could not be
used. This bug has been fixed
An error in the XYZAddIsoLines function has been fixed.
UniScript-Debugger: The debug window (ALT+3) did not display the right
variables.
Placeholder: If a table object contained a placeholder which could not
replaced by a value from an NC file the placeholder would not be removed.
The RegisterFunction documentation was wrong. The documentation has
been fixed.
IC-Editor: The edior could sometimes not save a file on a network drive
when the serve was running Windows NT 4.0.
Akims spline: The function to calculate the akima spline did not
compute the last data point correctly. Sometimes the last point was a huge
negative numer.
Formula Interpreter: The min(), max() function did not calculate the
min, max values element wise. Instead it calculated the min/max value for
the complete channel. The counter() Function falied to be calculated. These
bugs have been fixed.
Data Editor: The copy to clipboard function failed, when the data
contained missing values.
Data Editor: For some netCDF files the C_format attribute was not
evaluated correctly.
1D-Dataset: The paratmeters xStart und xDelta were set to 0 and 1 for UniPlot 2.x
and UniPlot 3.x documents ignoring their real value. This bug has been fixed.
Diagram Grid Lines: Grid Lines could only be drawn with a solid line style.
This bug has been fixed.
Style Files: In the new XML based style files introduced with UniPlot 4.0.3
special characters e.g. ä, ü, ß, could not be used for style names. This bug has been fixed.
3D-Dataset: The non linear interpolation could fail if the x- or y-coordinates
were given as constant cross sections (e.g. rpm = 1000, 2000, etc). This bug has been fixed.
The nonlin function had a memory leak.
The TableSetBrushIndex caused an error if invoked with three
parameters
The dcoumentaion of the TableCreate(nColumns, nRows) function had
an error.
The XYZGetBubbleSize functions returned the size in steps of 0.01
centimeters instead of centimeters.
Compatibility problems between UniPlot 3.x and UniPlot 4: In UniPlot 3.x
global variables could be used in a function without being declared at the
beginning of the function. This bug has been fixed in UniPlot 4. In
UniPlot 4 each global varialbe must be declared at the beginning of the
function (global var1, var2;).
Unfortunately, this caused problems with older script files. To return to
the old behavior, you can insert the line config("no-global-redeclaring", 1)
at the beginning of the file. Example:
config("no-global-redeclaring", 1)
def test1()
{
global a;
a = 123;
}
def test2()
{
print a;
}
test1();
test2(); /* prints 123 */
The MessageBoxError function caused an memory violation error if the
first parameter was an empty string, e.g.: MessageBoxError(strempty(1,1)).
The functions XYZShowIsolines and XYZIsIsolinesVisible were
missing in UniPlot 4.0.0 to UniPlot 4.0.2.
Polar Plot: The curve was drawn from the last data point to an arbitrary
data point outside the plot.
Dataset List: The Data=>Dataset List dialog box could not be opened
with a right mouse click inside the diagram. This bug has been fixed.
NOT_FOUND: Placeholder values which could not be found in the specified
NC file were replaced by the text NOT_FOUND. The text NOT_FOUND has been replaced by
an empty string.
If the diagram size or position were manipulated using the arrow keys
UniPlotwould cause a memory violation error in some circumstances.
The rs_pdsi.ini files were overwritten during the installation
process. The new setup program writes the file rs_pdsi.ini.org.
Excel-Report: The report function File=>More File Functions=>Excel Report
failed if the directory was specified in the Tools=>More Options dialog
box as an UNC path, e.g. \\p700\c\protokolle.
Excel-Report: The _Report_SetNumberFormat() in the script file
rs_table.ic had a typing error in line 640.
3D dataset: The function to calculate the data hull of a 3D dataset had
an error if the data of the dataset was replaced. The function name was
extended by multiple times by the string wotcurve(xx,x,x,x).
XML: The element handler XML_Parse had a memory leak of 48 bytes.
Copy Datasets: XY datasets containing filter functions were not copied
correctly. This bug lead to an incorrect curve on the plot which was easy to
see. Because of this bug UniPlot version 4.0.0 and 4.0.1 should no
longer be used. The bug has been fixed.
When a file was to be printed, e.g. while creating a PDF-File, the file
name was cut off at 31 characters. The PDF file name was then incomplete.
This bug has been fixed.
Sometimes UniScript's run time error messages were incorrect. This bug
has been fixed.
X-Scale: Negative offset values could not be specified (see
Filter Functions for XY datasets, scale_x). This bug has been
fixed.
Exchange Datasource: The dialog box to select the data files had an error.
Data could not be selected using the >>> button. The bug has been
fixed.
3D-Matrix-Dataset Import: An error in the import function meant that
files that had empty rows before the matrix were not loaded. This error
appeared, for example, when loading a matrix that was created with the
Helios-System. This bug has been fixed.
The documentation of the functions XYZGetBubbleAttribute,
XYZGetBubbleSize, XYZIsBubbleVisible, XYZSetBubbleAttribute,
XYZSetBubbleSize, XYZShowBubble has been added.
The UniPlot setup program created two UniPlot icons on the desktop. This
bug has been fixed.
The strtol function could not be invoked with two return parameters.
This bug has been fixed.
The MapSetAt function accepted in undefined third parameter without
throwing an exception. This bug has been fixed.
The uniplot/addin/rs_inter and rs_inter.adi files were
unnecessary and will be removed by UniPlot 4.0.2's setup program.
A list of known bugs in UniPlot 3.x can be found here:
Bugs in UniPlot 3.x
Copyright © 1996-2010
Uniplot Software GmbH, Germany.
| |
|
