diff --git a/codetestingplayground/trace-teardrops.circuit.tsx b/codetestingplayground/trace-teardrops.circuit.tsx new file mode 100644 index 00000000..bd0e2462 --- /dev/null +++ b/codetestingplayground/trace-teardrops.circuit.tsx @@ -0,0 +1,14 @@ +export default () => ( + + + + + +) diff --git a/docs/elements/trace.mdx b/docs/elements/trace.mdx index b48c01c6..0c2083ac 100644 --- a/docs/elements/trace.mdx +++ b/docs/elements/trace.mdx @@ -41,8 +41,36 @@ Here's a simple example connecting two components: | `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 }]` | +| `pcbTeardrops` | Enable automatic PCB teardrops | `true` | +| `pcbTeardropStart` | Teardrop at the start (from) of trace | `true` | +| `pcbTeardropEnd` | Teardrop at the end (to) of trace | `false` | | `pcbPathRelativeTo` | Port selector that `pcbPath` coordinates are relative to (defaults to the `from` port) | `".R1 > .pin2"` | +## PCB teardrops + +Set `pcbTeardrops` to widen traces at pad and via contacts after routing. +Use `pcbTeardropStart` and `pcbTeardropEnd` to override the `from` and `to` +endpoints. Omitted endpoint settings inherit `pcbTeardrops`. + +This example adds a teardrop at R1 while leaving the C1 end unchanged: + + ( + + + + + +) +`} /> + ## Connecting to Nets Traces can connect to named nets like power and ground: