graphviz issueshttps://gitlab.com/graphviz/graphviz/-/issues2023-02-25T00:44:46Zhttps://gitlab.com/graphviz/graphviz/-/issues/1346dot X11: nodes disappear on zoom or pan2023-02-25T00:44:46ZRobbie Huffmandot X11: nodes disappear on zoom or panI'm using dot interactively, and all the nodes disappear if any node is panned or zoomed off the left or bottom sides of the window. Cluster boxes and links remain. The nodes reappear if I move all the nodes back on to the window. But! B...I'm using dot interactively, and all the nodes disappear if any node is panned or zoomed off the left or bottom sides of the window. Cluster boxes and links remain. The nodes reappear if I move all the nodes back on to the window. But! But this only happens after dot re-reads an updated file.
If I open a file with "dot -Tx11" and move nodes off the side, it's fine. Once I change the contents, the nodes disappear.
This is on Ubuntu with version 2.38.0-12ubuntu2.
![graphviz-missing-nodes](/uploads/afc899a75e1fb8b355b605534113aa72/graphviz-missing-nodes.png)https://gitlab.com/graphviz/graphviz/-/issues/387[Dot] graph's aspect attribute cause dupliated edges in output image!2023-02-19T17:21:10ZSteve (Gadget) Barnes[Dot] graph's aspect attribute cause dupliated edges in output image!Ported Issue from Mantis
Original ID: 2330
Reported By: stonecheung
SEVERITY: CRITICAL
Submitted: 2013-08-15 07:04:06
OS: ALL
OS BUILD: ALL
PLATFORM: ALL
## DESCRIPTION
## A simple test.dot file contains bidirected edge and with aspe...Ported Issue from Mantis
Original ID: 2330
Reported By: stonecheung
SEVERITY: CRITICAL
Submitted: 2013-08-15 07:04:06
OS: ALL
OS BUILD: ALL
PLATFORM: ALL
## DESCRIPTION
## A simple test.dot file contains bidirected edge and with aspect attribute set to 1.
digraph test {
graph [aspect=1];
"Point1" -> "Point2" [];
"Point2" -> "Point1" [];
## }
When this test.dot file processed by graphviz application(both command-line and GUI tool), the output image will contain 4 extra "Point2" -> "Point1" edge eages(seems the "Point2" -> "Point1" edge duplicated)!
If remove the graph's aspect attribute, everything will be OK!
## STEPS TO REPRODUCE
## A simple test.dot file contains bidirected edge and with aspect attribute set to 1.
digraph test {
graph [aspect=1];
"Point1" -> "Point2" [];
"Point2" -> "Point1" [];
## }
When this test.dot file processed by graphviz application(both command-line and GUI tool), the output image will contain 4 extra "Point2" -> "Point1" edge eages(seems the "Point2" -> "Point1" edge duplicated)!https://gitlab.com/graphviz/graphviz/-/issues/1645[feature suggestion] Allow edge ordering performed by both "in" and "out" dir...2023-02-18T16:44:15Zyuri[feature suggestion] Allow edge ordering performed by both "in" and "out" directions: add "both" to the "ordering" attributeI use graphviz to draw a computation graph. There are functions that generally accept several inputs and produce several outputs. When shown visually, order of both outputs and inputs is important because showing the edges comimg in and ...I use graphviz to draw a computation graph. There are functions that generally accept several inputs and produce several outputs. When shown visually, order of both outputs and inputs is important because showing the edges comimg in and out of nodes in a wrong order is confusing and doesn't match the entity being represented.
Documentation (https://www.graphviz.org/doc/info/attrs.html#d:ordering) implies that the "outgoing" attribute can be ether "in" or "out". I suggest to add "both" such that a computation graph described above can be naturally represented.
There is a corner case when Node1 produces Edge1 and Edge2, but Node2 consumes Edge2 and Edge1, in that order. A case like this would be impossible to represent with "Node1 -> Node2" syntax. This needs to be dealt with somehow, but this problem is the problem of the DOT syntax, not of the underlying directed graph that it describes.https://gitlab.com/graphviz/graphviz/-/issues/162[Dot] [minlen=0] adds extra edges with multiple clusters2023-02-18T16:42:51ZSteve (Gadget) Barnes[Dot] [minlen=0] adds extra edges with multiple clustersPorted Issue from Mantis
Original ID: 2550 **_Referenced Attachment is only available in the original Mantis DB**_
Reported By: truss
SEVERITY: IMPORTANT
Submitted: 2015-06-04 23:51:29
OS: WINDOWS 8
OS BUILD: 8
PLATFORM: WINDOWS
## D...Ported Issue from Mantis
Original ID: 2550 **_Referenced Attachment is only available in the original Mantis DB**_
Reported By: truss
SEVERITY: IMPORTANT
Submitted: 2015-06-04 23:51:29
OS: WINDOWS 8
OS BUILD: 8
PLATFORM: WINDOWS
## DESCRIPTION
Attached dot file is the 'smallest' example in which multiple-edges are rendered (C->D). However, with more nodes within each cluster, the behavior is inconsistent and happens across arbitrary pairs of nodes across clusters.
In larger examples, if the [minlen=0] is retained the edges are drawn in order expected. However, if nothing but the offending [minlen=0] is removed, then the rest of the layout is now distorted.
## STEPS TO REPRODUCE
```
strict digraph G {
ordering=out;
subgraph cluster_1{
A;B;C;
}
subgraph cluster_2{
D
}
A->B ;
A->C ;
C->D [minlen=0];
}
```https://gitlab.com/graphviz/graphviz/-/issues/257[Dot] Erroneously duplicated edge between clusters2023-02-18T16:42:19ZSteve (Gadget) Barnes[Dot] Erroneously duplicated edge between clustersPorted Issue from Mantis
Original ID: 1622 **Attached file(s) currently only available on Mantis**
Reported By: Ben Butler-Cole
SEVERITY: MAJOR
Submitted: 2009-06-17 17:24:26
OS: _-_-*
VERSION: 2.23.20090616.0445
## DESCRIPTION
<br>
...Ported Issue from Mantis
Original ID: 1622 **Attached file(s) currently only available on Mantis**
Reported By: Ben Butler-Cole
SEVERITY: MAJOR
Submitted: 2009-06-17 17:24:26
OS: _-_-*
VERSION: 2.23.20090616.0445
## DESCRIPTION
<br>
The attached input (processed with 'dot -Tpng -otmp.png tmp.dot')
produces output with an extra edge (between nodes a and c).
<br>
This appears to be a minimal repro case: removing any of the nodes,
edges, clusters or constraint specifiers makes the problem go away.
<br>
Output in dot format contains only the expected edges.
## STEPS TO REPRODUCE
```
digraph G {
subgraph cluster_one {
a;
b;
}
subgraph cluster_two {
c;
}
a -> b [constraint=false];
a -> c [constraint=false];
}
```https://gitlab.com/graphviz/graphviz/-/issues/359[Dot] [dot] aspect attribute make duplicated edges in output image!2023-02-18T16:41:41ZSteve (Gadget) Barnes[Dot] [dot] aspect attribute make duplicated edges in output image!Ported Issue from Mantis
Original ID: 2365
Reported By: stonecheung
SEVERITY: CRITICAL
Submitted: 2013-09-13 11:19:41
OS: ALL
OS BUILD: ALL
PLATFORM: ALL
## DESCRIPTION
## A simple test.dot file contains bidirected edge and with aspe...Ported Issue from Mantis
Original ID: 2365
Reported By: stonecheung
SEVERITY: CRITICAL
Submitted: 2013-09-13 11:19:41
OS: ALL
OS BUILD: ALL
PLATFORM: ALL
## DESCRIPTION
## A simple test.dot file contains bidirected edge and with aspect attribute set to 1.
digraph test {
graph [aspect=1];
"Point1" -> "Point2" [];
"Point2" -> "Point1" [];
## }
When this test.dot file processed by graphviz application(both command-line and GUI tool), the output image will contain 4 extra "Point2" -> "Point1" edge eages(seems the "Point2" -> "Point1" edge duplicated)!
If remove the graph's aspect attribute, everything will be OK!
## STEPS TO REPRODUCE
## A simple test.dot file contains bidirected edge and with aspect attribute set to 1.
digraph test {
graph [aspect=1];
"Point1" -> "Point2" [];
"Point2" -> "Point1" [];
## }
When this test.dot file processed by graphviz application(both command-line and GUI tool), the output image will contain 4 extra "Point2" -> "Point1" edge eages(seems the "Point2" -> "Point1" edge duplicated)!
https://gitlab.com/graphviz/graphviz/-/issues/656[Dot] Constraint / Subgraph2023-02-18T16:40:44ZSteve (Gadget) Barnes[Dot] Constraint / SubgraphPorted Issue from Mantis
Original ID: 1888
Reported By: sdf894
SEVERITY: MAJOR
Submitted: 2010-05-22 14:49:23
OS: _-_-
VERSION: 2.26.3
## DESCRIPTION
<br>
There might be a possible bug when a "box" is part of two unconstrained
relat...Ported Issue from Mantis
Original ID: 1888
Reported By: sdf894
SEVERITY: MAJOR
Submitted: 2010-05-22 14:49:23
OS: _-_-
VERSION: 2.26.3
## DESCRIPTION
<br>
There might be a possible bug when a "box" is part of two unconstrained
relations and one relation(edge) leads into another subgraph,
the edge between the two subgraphs is doubled.
<br>
<br>
Here are two simple examples:
<br>
# <CD>
# ===[ incorrect ]==================================================
Digraph g {
<br>
node [shape=box];
<br>
subgraph cluster1 {
label="X";
A;
B;
C;
}
subgraph cluster0 {
label="Y";
Q;
}
C->B [constraint=false];
A->B [constraint=false];
A->Q [constraint=false];
}
<br>
#
# ===[ correct ]====================================================
<br>
Digraph g {
<br>
node [shape=box];
<br>
subgraph cluster1 {
label="X";
A;
B;
C;
}
subgraph cluster0 {
label="Y";
Q;
}
C->B [constraint=false];
A->B;
A->Q [constraint=false];
}
</CD>
<br>
I reported that possible bug once before, but now I figured out a
possible reason.
<br>
Hope this helps.https://gitlab.com/graphviz/graphviz/-/issues/258[Dot] Edge between clusters gets duplicated2023-02-18T16:40:30ZSteve (Gadget) Barnes[Dot] Edge between clusters gets duplicatedPorted Issue from Mantis
Original ID: 2455
Reported By: DelTree
SEVERITY: IMPORTANT
Submitted: 2014-05-15 13:32:21
OS: DEBIAN GNU/LINUX
## DESCRIPTION
An edge with [constraint=none] between two clusters gets duplicated.
## STEPS TO RE...Ported Issue from Mantis
Original ID: 2455
Reported By: DelTree
SEVERITY: IMPORTANT
Submitted: 2014-05-15 13:32:21
OS: DEBIAN GNU/LINUX
## DESCRIPTION
An edge with [constraint=none] between two clusters gets duplicated.
## STEPS TO REPRODUCE
The simplest file I found to exhibit the bug goes like this
```
digraph G
{
subgraph cluster_G1
{
{
rank=same;
A -> B;
}
C -> A;
}
subgraph cluster_G2
{
{
rank=same;
D -> E;
}
F -> E;
}
B -> D [ constraint=none ];
}
```
then I build with
`dot -Tpdf dupedge.gv -o dupedge.pdf`
## ADDITIONAL INFORMATION
I found the bug in debian version (2.26.3) and built version 2.38.0 to check. Same situation.https://gitlab.com/graphviz/graphviz/-/issues/2330an orthogonal edge doesn't connect to a triangle node2023-02-17T15:59:15ZCosta Shulyupincosta.shul@redhat.coman orthogonal edge doesn't connect to a triangle node## Steps to reproduce
```
graph {
layout=neato
splines=ortho;
0 [pos="0,0!"]
node [shape=triangle];
1 [pos="1,0.5!"]
2 [pos="2,0.4!"]
0 -- 1 [color=green4];
0 -- 2 [color=red];
}
```
[![Screenshot_from_2022-12-23_05-59-25](/uplo...## Steps to reproduce
```
graph {
layout=neato
splines=ortho;
0 [pos="0,0!"]
node [shape=triangle];
1 [pos="1,0.5!"]
2 [pos="2,0.4!"]
0 -- 1 [color=green4];
0 -- 2 [color=red];
}
```
[![Screenshot_from_2022-12-23_05-59-25](/uploads/20bd45b7fd92ae968d983affb8a861b2/Screenshot_from_2022-12-23_05-59-25.png)](
http://magjac.com/graphviz-visual-editor/?dot=graph%20%7B%0A%09layout%3Dneato%0A%09splines%3Dortho%3B%0A%090%20%5Bpos%3D%220%2C0%21%22%5D%0A%09node%20%5Bshape%3Dtriangle%5D%3B%0A%091%20%5Bpos%3D%221%2C0.5%21%22%5D%0A%092%20%5Bpos%3D%222%2C0.4%21%22%5D%0A%090%20--%201%20%5Bcolor%3Dgreen4%5D%3B%0A%090%20--%202%20%5Bcolor%3Dred%5D%3B%0A%7D%0A)
- Expected Behaviour: Green edge
- Actual Behaviour: Red edge
- OS Version: Ubuntu 22.04, any
- graphviz version 7.0.5~dev.20221215.0348 (20221215.0348)https://gitlab.com/graphviz/graphviz/-/issues/2346Label of edge not displayed when having "rank=sink"2023-02-15T01:33:11ZPlantUMLLabel of edge not displayed when having "rank=sink"## Steps to reproduce
In some case, the label of edge is not printed.
See the following example:
```
digraph unix {
{rank=sink;footer;}
subgraph cluster1 {
node1;
node2;
}
footer->node2;
node1->footer[label="should be...## Steps to reproduce
In some case, the label of edge is not printed.
See the following example:
```
digraph unix {
{rank=sink;footer;}
subgraph cluster1 {
node1;
node2;
}
footer->node2;
node1->footer[label="should be printed"];
}
```
## Expected Behaviour
The label should be printed, like in the following example:
```
digraph unix {
subgraph cluster1 {
node1;
node2;
}
footer->node2;
node1->footer[label="should be printed"];
}
```
## Graphviz Version
Graphviz 2.38.0 and Graphviz 2.43.0, at least.https://gitlab.com/graphviz/graphviz/-/issues/767[Dot] Generate easier output for SVG 'rounded,filled' boxes2023-02-12T02:11:23ZSteve (Gadget) Barnes[Dot] Generate easier output for SVG 'rounded,filled' boxesPorted Issue from Mantis
Original ID: 1596
Reported By: Egon Kastelijn
SEVERITY: MINOR
Submitted: 2009-04-28 18:04:54
OS: *-LINUX-FEDORA 10
VERSION: 2.16.1-0.6.FC10
## DESCRIPTION
<br>
Graphviz Dot can generate SVG files for 'rounde...Ported Issue from Mantis
Original ID: 1596
Reported By: Egon Kastelijn
SEVERITY: MINOR
Submitted: 2009-04-28 18:04:54
OS: *-LINUX-FEDORA 10
VERSION: 2.16.1-0.6.FC10
## DESCRIPTION
<br>
Graphviz Dot can generate SVG files for 'rounded,filled' boxes that are defined like this:
<br>
digraph process
{
graph [rankdir=TB]
<br>
ff [shape="box" style="filled,rounded"];
}
<br>
When Dot is used to generate the SVG file, (dot ff.dot -Tsvg -o ff.svg) then the filling of the rounded corners of the box are drawn like this:
<path style="fill:lightgrey;stroke:lightgrey;" d="M12,-36C6,-36 1.83557e-14,-30 1.53951e-14,-24"/>
<br>
And the stroke is drawn like this:
<path style="fill:none;stroke:black;" d="M12,-36C6,-36 1.83557e-14,-30 1.53951e-14,-24"/>
<br>
This is a rather complex way to generate rounded corners.
There is an easier way to generate SVG rounded corners.
(the way Inkscape generates them)
<CD>
<rect
style="fill:#ffff00"
id="rect2383"
width="368.57144"
height="257.14285"
x="120"
y="186.6479"
ry="12.595651" />
</CD>
<br>
This way you only need to specify the roundness of the corners using 'ry'.
<br>
Why do I think this should be changed?
The current way of generating SVG rounded corners does not allow for easy post-processing of the generated SVG.
For example, this script does not work nicely on SVG:
<br>
http://www.hokstad.com/making-graphviz-output-pretty-with-xsl.html
<br>
kind regards,
<br>
Egon Kastelijnhttps://gitlab.com/graphviz/graphviz/-/issues/815[Output Generation] option to not add style attributes in svg output2023-02-12T02:10:36ZSteve (Gadget) Barnes[Output Generation] option to not add style attributes in svg outputPorted Issue from Mantis
Original ID: 1469
Reported By: Thomas Koch
SEVERITY: MINOR
Submitted: 2008-10-31 10:44:52
OS: X86-LINUX-DEBIAN LENNY
VERSION: 2.20.2
## DESCRIPTION
<br>
I want to format my SVG with a CSS Stylesheet, but I c...Ported Issue from Mantis
Original ID: 1469
Reported By: Thomas Koch
SEVERITY: MINOR
Submitted: 2008-10-31 10:44:52
OS: X86-LINUX-DEBIAN LENNY
VERSION: 2.20.2
## DESCRIPTION
<br>
I want to format my SVG with a CSS Stylesheet, but I can not set the styles (fill, stroke) that have already been set by the style attribute of the elements.
<br>
Proposed solutions:
<CD>
1. Do not add any styles to the svg as long as stylesheet is set
2. Add an extra dot attribute to indicate whether styles should be set
3. Do not set styles in the elements, but in a central style section in the svg defs area and include a user defined stylesheet after this inline style tag.
</CD>https://gitlab.com/graphviz/graphviz/-/issues/1226newrank=true does not handle source/min/max/sink correctly.2023-02-11T16:46:35ZJohn Ellsonnewrank=true does not handle source/min/max/sink correctly.*Created by: emden*
If the graph
```c
digraph {
a -> b
{ rank=source c]
{ rank=sink d}
}
```
is processed with dot -Gnewrank, c and d are placed on the same rank as a.
![out](https://cloud.githubusercontent.com/assets/1530174/2...*Created by: emden*
If the graph
```c
digraph {
a -> b
{ rank=source c]
{ rank=sink d}
}
```
is processed with dot -Gnewrank, c and d are placed on the same rank as a.
![out](https://cloud.githubusercontent.com/assets/1530174/24715848/f8225f24-19fa-11e7-9a0f-1ef34906fc65.png)
The expected output is
![out0](https://cloud.githubusercontent.com/assets/1530174/24715906/2eafacc2-19fb-11e7-9899-76b44e09f7f2.png)
The same happens if source and sink are replaced by min and max.https://gitlab.com/graphviz/graphviz/-/issues/883[Neato] Multi-image output to non-PS formats for multi-layer graph2023-02-09T15:44:34ZSteve (Gadget) Barnes[Neato] Multi-image output to non-PS formats for multi-layer graphPorted Issue from Mantis
Original ID: 1271
Reported By: Max Alekseyev
SEVERITY: MINOR
Submitted: 2008-03-05 04:49:44
OS: _-_-
VERSION: 2.16
## DESCRIPTION
<br>
It would be useful to output a multi-layer graph into a sequence of imag...Ported Issue from Mantis
Original ID: 1271
Reported By: Max Alekseyev
SEVERITY: MINOR
Submitted: 2008-03-05 04:49:44
OS: _-_-
VERSION: 2.16
## DESCRIPTION
<br>
It would be useful to output a multi-layer graph into a sequence of images (one per a layer).
In particular, this feature would allow to use output formats that do not support multi-page content.
<br>
Also, it would be also useful to have a command line option that specifies a particular layer for output.
<br>
Thanks,
Max
## ADDITIONAL INFORMATION
[ellson]
You can generate multiple layer images into any output format that allows multiple images. At the moment this is -Tps
and -Tswf (if graphviz is built with libming). I think SVG could support multiple pages, but thats not implemented yet.
-Tpng doesn't support multiple images in a single file, AFAIK. Some possibilies:
<CD>
- extend funtionality of -O to generate a uniquely named png image file for each layer.
- add support for -Tmng
- add support for the animated GIF format (what is it called?)
- extend SVG support to multiple pages.
</CD>
All these options just require some coding. All the hooks are in place at the plugin interface to provide layers to
any format that can handle them.
For now I recommend that you use -Tps for layered, or other multipage, graphs.https://gitlab.com/graphviz/graphviz/-/issues/1964Cluster horizontal margin not working2023-02-09T15:42:21ZRodrigo PelorossoCluster horizontal margin not workingHi! I'm trying to add different vertical and horizontal margins to a cluster, but it doesn't seem to be working. Am I making any mistake? Thank you!
## Steps to reproduce
I rendered the following graph (which is the cluster demo graph ...Hi! I'm trying to add different vertical and horizontal margins to a cluster, but it doesn't seem to be working. Am I making any mistake? Thank you!
## Steps to reproduce
I rendered the following graph (which is the cluster demo graph with a small modification to add margins to cluster_1)
```
digraph G {
subgraph cluster_0 {
style=filled;
color=lightgrey;
node [style=filled,color=white];
a0 -> a1 -> a2 -> a3;
label = "process #1";
}
subgraph cluster_1 {
node [style=filled];
b0 -> b1 -> b2 -> b3;
label = "process #2";
color=blue
margin="50,0"
}
start -> a0;
start -> b0;
a1 -> b3;
b2 -> a3;
a3 -> a0;
a3 -> end;
b3 -> end;
start [shape=Mdiamond];
end [shape=Msquare];
}
```
## Expected Behaviour
According to the [documentation](https://graphviz.org/doc/info/attrs.html#d:margin) I should be able to specify vertical and horizontal margins to a cluster, passing a point instead of a scalar.
So in this example I would expect cluster_1 to have 50 as horizontal margin and 0 as vertical margin.
## Actual Behaviour
It is only taking the first attribute of the point as margin, applying 50 to the vertical and horizontal margin.
## OS Version
ArchLinux, kernel: 5.10.16-arch1-1
## Graphviz Version
dot - graphviz version 2.46.0 (0)https://gitlab.com/graphviz/graphviz/-/issues/740[Output Generation] Allow different colors on different peripheries2023-02-09T15:35:57ZSteve (Gadget) Barnes[Output Generation] Allow different colors on different peripheriesPorted Issue from Mantis
Original ID: 1694
Reported By: Lukasz Rymko
SEVERITY: MINOR
Submitted: 2009-08-18 22:00:57
OS: _-_-
VERSION: 2.25
## DESCRIPTION
<br>
i am using graphviz in my Java application for representing relations bet...Ported Issue from Mantis
Original ID: 1694
Reported By: Lukasz Rymko
SEVERITY: MINOR
Submitted: 2009-08-18 22:00:57
OS: _-_-
VERSION: 2.25
## DESCRIPTION
<br>
i am using graphviz in my Java application for representing relations between employees. You're doing a great job. I think it will be a nice feature if you'd add a possiblity to draw multiple peripheries with different colours.
## ADDITIONAL INFORMATION
[erg] Also see bug 1674.https://gitlab.com/graphviz/graphviz/-/issues/2310SVG output should link edges to nodes2023-02-09T14:59:10ZNathan WillisSVG output should link edges to nodes## Summary
SVGs, regardless of layout, currently consist of node and edge elements that are placed independently on the canvas. That makes them extremely finicky to adjust with manual tweaking (such as in Inkscape) without edges becomin...## Summary
SVGs, regardless of layout, currently consist of node and edge elements that are placed independently on the canvas. That makes them extremely finicky to adjust with manual tweaking (such as in Inkscape) without edges becoming disconnected from their nodes.
It is possible to generate more tool-friendly SVGs in this respect. Namely, the behavior I would most like to see is an approach paraellel to what iGraph employs:
- Nodes and Edges are added as separate layers in the SVG.
- Edges are linked to Nodes via Inkscape's `diagram connector` mechanism
Those two features, together, give users the ability to edit the SVG output in Inkscape when necessary without garbling up its component elements, but also do so _without_ affecting the SVG's readability to read-only tools.
### Quick background
I'm a postgraduate research student currently caught right in between GraphViz and iGraph for a few key bits. GraphViz's output (unlike igraph) preserves `class` attributes, which is fantastic, but I also periodically need to manually make tweaks to graph layout (which puts me in the reverse bind: igraph supports it, but erases the attributes on the nodes and edges).
## Documentation of desired behavior
This is the issue in which the iGraph team implemented the SVG modifications mentioned above:
https://github.com/igraph/igraph/issues/246
This is some Inkscape documentation about the "diagram connector" type:
https://archive.flossmanuals.net/inkscape/toolbox/connector-tool.html
https://wiki.inkscape.org/wiki/Connector_tool_tutorial
I am, of course, aware that this element is not part of the original SVG spec (although that could change); however, it is an extension and the Inkscape-specific parts are ignored, in my tests, by other SVG renderers. And, I suppose, it's worth also noting that Inkscape is FOSS and thus is not locking-in the user or the document.
## OS Version
Personally I run Linux; mostly Ubuntu LTS, at the moment 22.04, but I think this is corss-platform.
## Graphviz Version
2.43.0 (0)
## Additional info
I know this is a feature request, and I know not everyone CARES about manually tweaking SVG output. But in some fields, it makes a huge difference when you're trying to communicate network concepts.https://gitlab.com/graphviz/graphviz/-/issues/2353rank=source seems to be ignored2023-02-09T14:55:40Zsteve roushrank=source seems to be ignored## Steps to reproduce
`dot -Tpng badRank0.gv >badRank0.png`
The source:
```
digraph{
rankdir = LR;
{
rank="source";
Sa;
Sb;
Sc;
St;
}
St -> {t_1[label="t",shape=plaintext]...## Steps to reproduce
`dot -Tpng badRank0.gv >badRank0.png`
The source:
```
digraph{
rankdir = LR;
{
rank="source";
Sa;
Sb;
Sc;
St;
}
St -> {t_1[label="t",shape=plaintext];}
Na;
{t_a[label="t",shape=plaintext];}->Na
Sa->Na;
Sb->Na;
Sc->Na;
subgraph cluster_b {
fillcolor = "#ddDDdd";
style=filled;
label="";
Nb1;
Nb;
Nb1->Nb;
}
{t_2[label="t",shape=plaintext];}->Nb1
Sa->Nb;
Nc;
{t_c[label="t",shape=plaintext];}->Nc
Nd;
{t_d[label="t",shape=plaintext];}->Nd
Na->Nd;
Nb->Nc;
Nd->O1;
Nc->Nd;
{
rank="sink";
O1;
}
}
```
## Expected Behaviour
Only the nodes named _S?_ would be on _min_ (leftmost) rank (see https://graphviz.org/docs/attrs/rank/)
## Actual Behaviour
The desired nodes are not on the minimum rank.
![badRank0](/uploads/59e5c872cc6fa1a3002a3265ae67ebc7/badRank0.png)
## OS Version
Linux under Windows (WSL2)
`Linux NewWin 5.15.79.1-microsoft-standard-WSL2 #1 SMP Wed Nov 23 01:01:46 UTC 2022 x86_64 x86_64 x86_64` G
## Graphviz Version
`dot - graphviz version 7.0.7~dev.20230106.0633 (20230106.0633)`
## Additional info
Fill in with anything else that might be important.https://gitlab.com/graphviz/graphviz/-/issues/1312Tooltips for pie wedges?2023-02-09T14:53:10ZGraham HanningtonTooltips for pie wedges?I'm using `style=wedged` to render nodes as pie charts. Works great.
I'm using the node tooltip to display numerical figures for the pie:
tooltip="Tran ROOT #141: &#xA;Response .0030&#xA;UserCPU .0003&#xA;Suspend .0026"
I'd prefer...I'm using `style=wedged` to render nodes as pie charts. Works great.
I'm using the node tooltip to display numerical figures for the pie:
tooltip="Tran ROOT #141: 
Response .0030
UserCPU .0003
Suspend .0026"
I'd prefer to set a tooltip on each wedge, with the specific figure for that wedge.
Also (but lower priority): I'd like to set an id attribute value (in the output SVG) on each wedge (`<path id="...">`).https://gitlab.com/graphviz/graphviz/-/issues/2349dotguide document is unclear regarding dot's four phases2023-02-06T21:04:50Zsteve roushdotguide document is unclear regarding dot's four phases## Steps to reproduce
Read unclear documentation
## Expected Behaviour
the [dotguide.pdf](http://www.graphviz.org/pdf/dotguide.pdf) document states that dot is comprised of _four_ phases. I expect it to then list the _four_ phases.
...## Steps to reproduce
Read unclear documentation
## Expected Behaviour
the [dotguide.pdf](http://www.graphviz.org/pdf/dotguide.pdf) document states that dot is comprised of _four_ phases. I expect it to then list the _four_ phases.
## Actual Behaviour
The document then seems to list _five_ "steps" (apparently step==phase). My guess is that steps 1 & 2 == phase 1, but this is only a guess.
## OS Version
web-site based documentation
## Graphviz Version
all
## Additional info
From page 2, slightly reformatted:
> **dot** draws graphs in _four_ main phases. Knowing this helps you to understand
> what kind of layouts dot makes and how you can control them. The layout procedure used by dot relies on the graph being acyclic.
>
> Thus, the _first_ step is to break
> any cycles which occur in the input graph by reversing the internal direction of
> certain cyclic edges.
> The _next_ step assigns nodes to discrete ranks or levels. In a
> top-to-bottom drawing, ranks determine Y coordinates. Edges that span more than
> one rank are broken into chains of “virtual” nodes and unit-length edges.
> The _third_ step orders nodes within ranks to avoid crossings.
> The _fourth_ step sets X coordinates of nodes to keep edges short,
> and the _final_ step routes edge splines.