diff --git a/docs/elements/trace.mdx b/docs/elements/trace.mdx index 5ed11ec..788d291 100644 --- a/docs/elements/trace.mdx +++ b/docs/elements/trace.mdx @@ -39,6 +39,7 @@ Here's a simple example connecting two components: | `maxLength` | Maximum length the trace can be (optional) | `"10mm"` | | `minLength` | Minimum length the trace must be (optional) | `"5mm"` | | `width` | Width of the trace (optional) | `"0.2mm"` | +| `thickness` | Same as `width`; sets the copper width for the trace (optional) | `"0.2mm"` | | `pcbPath` | Array of points defining a manual PCB path relative to an anchor port | `[{ x: 1, y: 0 }, { x: 1, y: 1 }]` | | `pcbPathRelativeTo` | Port selector that `pcbPath` coordinates are relative to (defaults to the `from` port) | `".R1 > .pin2"` | @@ -152,3 +153,23 @@ When using net connections we use a Rats Nest on a PCB view or a net label on a schematic view. When you see a dotted line on a Rats Nest, you should think of it as a _possible_ connection point, but not necessarily the final place where the autorouter will connect to the net. + +## Creating a direct path with a custom thickness + +Use an empty `pcbPath` array to keep the autorouter's direct path between two +ports while overriding the trace width via the `thickness` property. + + ( + + + + + + ) +`} />