Recent changes to bugs

screenShot method messes up screenshots

Anonymous — Thu, 08 Apr 2010 13:42:36 -0000

The screenShot method from the GraphViewerRemote interface makes screenshots, but the size is wrong and the whole graph is there allright but not in the right place, there is a shift in both the x and y axis.
Please find the source code and the SVG pictures attached.
- screenshot.svg is the screenshot made by right-clicking ont the display window, that turns out to be correct
- capturegraph.svg is the file created by the screenShot method.
Thanks for the help.

screenShot method has no effect

Anonymous — Wed, 07 Apr 2010 16:02:48 -0000

The screenShot method from the GraphViewerRemote interface has no effect whatsoever. No file is created, and no error message is displayed either. Tried chmoding the directories to 777, no improvements were observed. (Tested on the example code provided in the tutorial)

problem in DGS parser with semi-numeric keys

Antoine — Sat, 30 Dec 2006 18:13:09 -0000

In the DGS graph reader, if the identifier of an element starts with a number but also contains letters the parser fails to read it correctly, for example:

an 123A A B

will fail since 123A is badly read.

Removed node not removed in the GraphViewer

Yoann — Thu, 21 Dec 2006 14:47:22 -0000

When I remove a node in a graph (org.miv.graphstream.graph.Graph), it is effectively remove from the graph. If a GRaphViewer was instantiated before that remove, then the node is not visually removed while it is in the "real" graph.

Inconsistancies when iterators remove elements

Yoann — Thu, 21 Dec 2006 13:29:05 -0000

In the class org.miv.graphstream.graph.Graph, methods getNodeIterator() and getEdgeIterator() return iterators that can remove elements in their structure. No control is made when the remove() method is called from these iterators. It results in inconsistencies in the Graph internal structure.