jim_jom@web.de

The ExportSvg.cpp has been changed May 2018. The PyPi Package is from November 2017. Maybe the bug is already fixed. Do you work on getting Tulip 5.2 into PyPi?

Will do as soon as I have a graphml file without sensitive information. It's kinda unfortunate that I can't redact those information because then the bug does not trigger. Only a few attribute values of edges/nodes are affected in large graphs. Workaround: Use GEXF. They are very similar formats. Downside: NetworkX does not export graph ("global") attributes in GEXF, only node and edge attributes. Transformation is quite easy: import networkx as nx nx.write_gexf( nx.read_graphml( "graph.graphml"...

Thanks for your reply. I managed to get it somewhat working in LXD/Docker by using Xvfb and installing tons of dependencies (probably more than needed). The script imports the GEXF, creates a hidden node-link window and then exports a PNG - which is working fine. The final PNG file contains the picture just like I need it. But somehow the SVG export still segfaults. Do you know if the SVG Export module is different to the PNG export in any way? How can I narrow down why it is faulting? The Dockerfile:...

Indeed, changing the graphics driver solved this problem. I am using the other internal graphics card with nvidia proprietary drivers.

Extremity scaling (arrows too small -> nearly invisible)

Drop Python 2, ship Python 3

"Tulip development is now hosted on GitHub by the way." Please put that on the website. I just created multiple bug reports here, because tulip.labri.vr told me to. -.-

Node/Edge selection tool slow on Linux