kvid

Another thing that might help, is to combine all invisible nodes on the same rank inside a sheathing into a common invisible node to avoid that Graphviz swap their order....

Inspired by a recent issue, I pick up this old thread again. How about specifying each heatshrink section as a separate bundle and splice the wires going through several bundles...

Thank you for reporting this strange error message. I admit it doesn't tell you much about what really is the problem. We are discussing how to improve error messages in...

To be able to reproduce your use case, please provide your version numbers and full input YAML as described in the [guidelines](https://github.com/formatc1702/WireViz/blob/master/docs/CONTRIBUTING.md). The error might be triggered by something in...

One idea that is developing in my mind, is to create a generic `Component` dataclass that contains all attributes that are common to all components, and then make the subclasses...

AFAIK, the wire gauge value is not currently inerpreted, but one approach could be to sort all unique gauge values, use the minimum thickness for the smallest mm^2 value (or...

If this is a wanted feature, then I can try to do this after https://github.com/formatc1702/WireViz/pull/17 is merged in.

I agree the current version (v0.3.2) doesn't handle such loops in the diagram very well, but there is an optional `loops` attribute you can use for connectors that should fit...

> I missed the loops attribute. That is, indeed, what I wanted. 👍 > > As mentioned in [#48](https://github.com/formatc1702/WireViz/issues/48), the length of the shorting wire needs some control. It overlapped...

> Currently, running WireViz generates multiple output files from the YAML input by default: > * `.png` raster image > * `.svg` vector image > * `.gv` GraphViz code >...