New username: @17o2

Even though I have not worked on this feature for a while, I have been using it in practice and it has proven quite robust. I would like to request...

- The branch has been rebased onto `dev` (using squash to avoid needing to solve merge conflicts on intermediate commits; a backup branch exists for now to preserve the original...

Thanks @awb1015 for the feedback! Usually I've waited for @kvid's approval before merging into `dev`, since he's quite good at catching edge cases, improving the code quality and providing generally...

> Prior to rebase I hadn't had any issues but now in the output `.png` I've noticed that the arrows between equivalent pins are not fully aligned to the row...

I just did a rebase onto `dev` since GitHub was reporting a small merge conflict before. It should not be related to the described issue of arrows not being aligned.

Yes please, a set of files for a minimal working example will be really helpful.

Please try the updated code; your bug should be fixed in 02a800abef3f35bdc4f8bbcafd9f50309a7cbe17. Root cause: - #229 changed the way connections between components are handled, by internally assigning unique IDs to...

All comments have been addressed inside https://github.com/formatc1702/WireViz/pull/251. Not merging yet since it would immediately push `dev` forward, but without the latest code suggestions. I will wait until #251 is merged...

@spanner888 I think what you mention is already being covered in #134.

A simple solution might be to allow every parameter of the cable/bundle to be either a string / int (applying it to all wires) or a list (length = wirecount),similar...