-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to draw wire studs? #417
Comments
So this is the best i can do, i wish we could make X3 view less anbiguous, for example if it could be a little higher the wiers bend would be more clear.
|
@0x0fe wrote:
Please help us understand what parts (of docs/examples/tutorial) are unclear, so we can try improving them. I assume you want two equal ferrules in your use case. Then you only need to define it once, e.g. like this: connectors:
F1:
style: simple # Single-pin connector with simplified rendering
type: Ferrule # Type of connector
color: OG # Optional color
# together with the other connectors Then you add connections:
- # 1st connection set
- # 2nd connection set
-
- X1: [1-2]
- W3: [1-2]
- F1. In rare cases you might want to specify designators to each ferrule instance, and then you can replace the simple |
@0x0fe wrote:
I can see the wire splines between W1 and X3 are a bit hard to separate. This layout is made by the Graphwiz back-end that probably optimize on shortest total spline lengths, and places X3 close to W2 because there are more splines between W2 and X3 than between W1 and X3. There are a couple of things you might try:
This is a combination of the two techniques, and you can try different tweak:
override:
graph:
ranksep: '3' # Global horizontal spacing (default 2)
append: |
"W3" -- "X3" [style=invis weight=2] // Invisible edge to bring X3 closer to W3 |
I am struggling to reproduce something like this, no problem with the conenctors, however i am really not sure how to generate the two wire studs (red and green) i tried to add two ferrules but i always get errors since the synthax of using ferrules is unclear.
The text was updated successfully, but these errors were encountered: