daVinci V1.4 bugreport
----------------------

This file contains informations about all known bugs of the interactive graph 
visualization system daVinci V1.4.

The bugreport is continuously updated on ftp.Uni-Bremen.DE (134.102.228.2) 
in file /pub/graphics/daVinci/bugreport.txt

Last update: 1995-05-30
===============================================================================
Bug Number:	01-V1.4
Finder:		Kurt Stenzel, University of Karlsruhe, Germany
Date:		1994-11-21	
Author:		Mattias Werner	
Affected:	daVinci V1.4
Subject: 	Menu 'Place visible Nodes' doesn't work in daVinci V1.4
Module: 	DrawingGridFunctions.AS, GraphToHierarchy.AS
Problem:	In most cases function 'Place visible Nodes' doesn't work.
		It displays an error message and terminates daVinci.
Reason:		There were several bugs, it would be too difficult to describe
		them in detail. Mostly they were due to the optimizations in
		V1.4. 
State:		Fixed in daVinci V1.4.1. (on ftp.uni-bremen.de, 1994-12-02).
===============================================================================
Bug Number:	02-V1.4
Finder:		Rick Vaupel, New Mexico State University, Las Cruces, USA.
Date:		1994-11-23	
Author:		Mattias Werner	
Affected:	daVinci V1.2 - V1.4
Subject: 	Bug in documentation of application commands
Module: 	user_manual.ps
Problem:	On page 36 of the user_manual.ps the application commands are
		listed. The two commands set_accuracy_phase1 and
		set_accuracy_phase2 have to be:
		  set_accuracy_phase_1 and set_accuracy_phase_2
		In the file example_commands.txt the usage is shown correctly.
State:		Fixed in daVinci V1.4.1. (on ftp.uni-bremen.de, 1994-12-02).
===============================================================================
Bug Number:	03-V1.4
Finder:		daVinci project, University of Bremen, Germany
Date:		1994-11-23	
Author:		Mattias Werner	
Affected:	daVinci V1.1 - V1.4
Subject: 	Relative paths in application commands don't work. 
Module: 	DaVinciNotifyFunctions.AS
Problem:	In the application commands dealing with filenames (i.e.
		load_graph) relative path/filenames don't work.
Reason:		The function that splits the filename into path and file
		added a '/' in front of the path. 
State:		Fixed in daVinci V1.4.1. (on ftp.uni-bremen.de, 1994-12-02).
===============================================================================
Bug Number:	04-V1.4
Finder:		daVinci project, University of Bremen, Germany
Date:		1994-12-08	
Author:		Mattias Werner	
Affected:	daVinci V1.4.1
Subject: 	Problems with Fine-Tuning and Selection.
Module: 	DaVinciManualLayout.AS, DaVinciWindowEvents.AS
Problem:	Fine-Tuning with Preserve Order in a scaled visualization
		doesn't work. Also you can't select multiple nodes with
		rubber banding in a scaled visualization.
Reason:		These two bugs were introduced while fixing bug 01-V1.4. :-(
		One internal function that needed unscaled coordinates in
		old versions, now needs scaled coordinates. We've missed to
		change two calls of the function.
State:		Fixed in daVinci V1.4.2. (on ftp.uni-bremen.de, 1995-01-12).
===============================================================================
Bug Number:	05-V1.4
Finder:		Berthold Hoffmann, University of Bremen, Germany
Date:		1994-12-15	
Author:		Michael Froehlich	
Affected:	daVinci V1.3 - V1.4.1
Subject: 	PostScript-files, generated by daVinci, may have errors.
Module: 	DaVinciGraphicalLibrary.AS
Problem:	daVinci PostScript files of graphs with a node text containing 
		the characters '(', ')' or '\' have errors. Especially,
		if the text of a node contains a '(' without a ')' and vice 
		versa, then the generated PostScript file is not working with 
		any printer or viewing tool.
Reason:		'(' and ')' are special characters for delimiting strings in
		PostScript, so they have to be escaped with a '\'. This wasn't
		considered in earlier versions of daVinci.
State:		Fixed in daVinci V1.4.2. (on ftp.uni-bremen.de, 1995-01-12).
===============================================================================
Bug Number:	06-V1.4
Finder:		Several Users
Date:		1994-12-19	
Author:		Mattias Werner	
Affected:	daVinci V1.4 documentation
Subject: 	Printing of User-Manual PostScript-file.
Module: 	user_manual.ps
Problem:	Some users of daVinci had problems printing the User Manual.
		They got one page with an error message saying:
		  "Can't select requested paper size for Frame print job!"
Reason:		There is a paper size specification part in the PostScript-
		File automatically generated by FrameMaker 4. Which defines
			%%BeginPaperSize: A4
			%%EndPaperSize
		in lines 1921 and 1922 of user_manual.ps.
		Patch: Please comment out the two lines in a text editor
		       by adding a '%' at the beginning of each line:
			% %%BeginPaperSize: A4
			% %%EndPaperSize
State:		Please use the US Letter documentation files on
		ftp.uni-bremen.de in /pub/graphics/daVinci/documentation_only.
===============================================================================
Bug Number:	07-V1.4
Finder:		Cliff Click, Hewlett-Packard Laboratories, Cambridge, MA
Date:		1994-12-12	
Author:		Mattias Werner	
Affected:	daVinci V1.2 - daVinci V1.4.1
Subject: 	daVinci on color platforms.
Module: 	Most of the *.xc Files
Problem:	On color platforms, users (including daVinci-project) often
		didn't get the expected colors in the daVinci window. This
		especially happened, if applications like mosaic or xv that
		use many colors were running on an 8-bit color platform.
		Another problem occurs on x-bit platforms that use neither
		0 nor (2^x)-1 as the color value for white.
Reason:		The first problem was solved by setting WIN_CMS for daVinci.
		Now the color map flips to the correct colors if you enter
		the daVinci window with the mouse pointer (only if there are
		not enough colors left when daVinci is started).
		To display graphs in the daVinci window, we use copy operations
		on pixmaps. There are exactly two pixmaps for each area of the
		graph. On one we display the nodes on the other the edges.
		By this trick, we can efficiently redraw parts of the graph.
		If we copy one pixmap onto the other, we need a transparent
		color but X doesn't support this. Normally (on Sun and Linux)
		we use white, because it has color value 0, which is transparent
		for a copy with OR. But X doesn't specify which color has value
		0. They especially say that you shouldn't use copy modes like
		OR and AND on color platforms. :-((
		Now we use a trick that makes white always the transparent color
		independent of the color value. This solves the second problem.
State:		Fixed in daVinci V1.4.2. (on ftp.uni-bremen.de, 1995-01-12).
===============================================================================
Bug Number:	08-V1.4
Finder:		Pery Pearson, Hewlett-Packard
Date:		1995-01-27	
Author:		Mattias Werner	
Affected:	daVinci V1.4.2 (only HP version)
Subject: 	Save PostScript dumps core on HP platforms.
Problem:	With some graphs the menu "Save PostScript..." dumps a
		core instead of creating a PostScipt file.
Reason:		Cliff Click from HP labratories, who did the HP port says:
		Apparantly the bug was caused by mixing a gcc compiled runtime
		system with cc compiled everything else (except for gcc compiled
		StreamIO) and linking with dynamic loading and shared libraries.
		Ugh. I recompiled the runtime with the native compiler and
		turned off dynamic loading and some shared libs (still
		XView is shared). In any case, the bug went away.
State:		Fixed for HP version (on ftp.uni-bremen.de, 1995-01-27).
===============================================================================
Bug Number:	09-V1.4
Finder:		Heiko Oehring, University of Karlsruhe, Germany
Date:		1995-05-22	
Author:		Michael Froehlich	
Affected:	daVinci V1.1 - V1.4.2 (all platforms)
Subject: 	daVinci terminates with "Internal error: Accessing 
		nonexistent argument of datatype keyOrReference 
		in module: DaVinciParser.AS, function: graphtree_graph.
Module: 	DaVinciParser.AS
Problem:	One will get this error message if a graph is loaded in term
		representation with a reference used as root node. E.g. this 
		one: a graph with two top-level nodes where the second is a 
		reference to the other one: 
			[l("Node 1",n("",[],[])),r("Node 1")]
Reason:		This is not a bug, but a semantical error previously 
		unhandled. References (to other nodes) can't be used as 
		root nodes, because in this situation it's not clear which 
		node should be the parent of the refered node (root nodes do
		not have any parents!). So references can only be used in  
		child node position of a term, e.g.
			[l("Node 1",n("",[],[r("Node 1"),...<more childs>]))]
State:		Curently unfixed. In the next daVinci release it will be 
		checked that references are not used in root node position. 
		Otherwise a non-terminating error message will be displayed. 
===============================================================================
Bug Number:	10-V1.4
Finder:		daVinci project, University of Bremen, Germany
Date:		1995-05-30	
Author:		Mattias Werner	
Affected:	daVinci V1.1 - V1.4.2 (all platforms)
Subject: 	daVinci and application hangs in pipe communication
Module: 	DaVinciCommunicationUnit.xc, GraphEditor.xc, application.c
Problem:	If the notifier for input on stdin is called by the X event
		handler, although there is nothing on stdin, daVinci and
		applications will hang.
Reason:		There was no check, if there is something on stdin. The
		read function was called directly, although there was nothing
		to read. This function than waits for input.
State:		Fixed for AIX version, because this is the version were it
		first occured. 
===============================================================================
