ab3204f9f1
The replaces the NextJS site powering FreeSewing.dev with a Docusaurus setup. It's part of my efforts to simplify FreeSewing's setup so we can focus on our core value proposition.
74 lines
1.9 KiB
Text
74 lines
1.9 KiB
Text
---
|
|
title: Path.trim()
|
|
---
|
|
|
|
The `Path.trim()` method Returns a new Path that is this path with overlapping
|
|
parts removed.
|
|
|
|
```js
|
|
Path path.trim()
|
|
```
|
|
|
|
|
|
|
|
<Example caption="Example of the Path.trim() method">
|
|
```js
|
|
({ Point, points, Path, paths, part }) => {
|
|
|
|
points.center = new Point(0, 0)
|
|
points.base = new Point(0, 10)
|
|
points.tip = new Point(0, 50)
|
|
points.tipCpRight = new Point(30, 50)
|
|
points.tipCpLeft = new Point(-30, 50)
|
|
paths.example = new Path().move(points.base)
|
|
for (let i = 0; i < 4; i++) {
|
|
points["base" + i] = points.base.rotate(60 * i, points.center)
|
|
points["tip" + i] = points.tip.rotate(60 * i, points.center)
|
|
points["tipCpRight" + i] = points.tipCpRight.rotate(60 * i, points.center)
|
|
points["tipCpLeft" + i] = points.tipCpLeft.rotate(60 * i, points.center)
|
|
if (i < 2) {
|
|
paths.example
|
|
.line(points["base" + i])
|
|
.curve(points["base" + i], points["tipCpLeft" + i], points["tip" + i])
|
|
.curve(
|
|
points["tipCpRight" + i],
|
|
points["base" + i],
|
|
points["base" + i]
|
|
)
|
|
} else {
|
|
paths.example
|
|
.line(points["base" + i])
|
|
.line(points["tip" + i])
|
|
.line(points["tipCpRight" + i])
|
|
.line(points["base" + i])
|
|
}
|
|
}
|
|
|
|
paths.offset = paths.example
|
|
.offset(10)
|
|
.setClass("lining dotted stroke-sm")
|
|
|
|
paths.trimmed = paths.offset
|
|
.trim()
|
|
.setClass("various stroke-xl")
|
|
.attr("style", "stroke-opacity: 0.5")
|
|
|
|
return part
|
|
}
|
|
```
|
|
</Example>
|
|
|
|
|
|
## Notes
|
|
|
|
This method is typically used when [Path.offset()](/reference/api/path/offset) caused some overlap.
|
|
However, use this sparsely or performance will suffer.
|
|
|
|
This method is recursive and complex, and the performance penalty for using
|
|
it on a long/complex path will be significant.
|
|
|
|
To limit the impact of path.trim(), follow this approach:
|
|
|
|
- construct a minimal path that contains the overlap
|
|
- trim it
|
|
- now join it to the rest of your path
|