Graphviz Issue Tracker - graphviz
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001470||graphviz||Dot||public||2008-10-31 17:56||2011-04-28 04:03|
|Status||acknowledged||Resolution||no change required|
|Platform||OS||x86-Windows-XP Pro||OS Version|
|Summary||0001470: width (36053 >= 32768) is too large|
I have a large dependency graph with 310 modules that was generated
by the "Project dependency graph generator" from here:
I manually invoke dot.exe like this:
dot -v -Tpng dep(sanitized).txt -o MySolution_dep.png
After lots of diagnostic messages, the last few are as follows:
network simplex: 100 200 300 400 500 600 700 800 900 1000
network simplex: 1100 1200 1300 1400 1500 1600 1700 1800 1900 2000
network simplex: 2100 2200 2300 2400 2500 2600 2700 2800 2900 3000
network simplex: 3100 3200 3300 3400 3500 3600 3700 3800 3900 4000
network simplex: 4100 4200 4300 4400
network simplex: 12018 nodes 18429 edges 4414 iter 4.23 sec
routesplines: 1229 edges, 13841 boxes 1.47 sec
Using render: cairo:cairo
Using device: png:cairo:cairo
dot: allocating a 334535K cairo image surface
dot: width (36029 >= 32768) is too large.
|Steps To Reproduce|
Some effort has been made to sanitize the input data. However, I ask
that you please keep the input data file private, and not make it
available on the web.
Please also do not make my e-mail address visible on the web.
I'm not sure I understand what the bug is. dot produces a layout which cannot fit into the
maximum size allowed for PNG output. It would be possible to put in code which, after
detecting this situation, would resize the output down to the maximum allowed. Usually,
however, we feel the solution is better left to the user. You can use the size attribute to
scale down the graph to an appropriate size; create output in a vector format like postscript
or svg; or alter the input graph or other of its parameters to get a smaller drawing.
We'll keep your input data private. It is our general policy to not post e-mail addresses.
> It would be possible to put in code which, after
> detecting this situation, would resize the output down to the maximum allowed.
Thats a reasonable solution.
[cox] Thanks for the speedy response and the suggestions! I hadn't tried using the size attribute before. So I read the documentation yesterday and gave it a try. Works great! That's what I needed to get around this issue. Much appreciated.
|Tags||No tags attached.|
|2011-04-28 04:03||user1||New Issue|
|2011-04-28 04:03||user1||Assigned To||=> user1|
|There are no notes attached to this issue.|