Holmes Futrell

My code may help here. BezierKit began as a Swift port of Bezier.js. I ran into the issues with reduce() and offset() mentioned in this thread, and fixed them. They're...

Hello @mbutterick Thank you once again for the level of detail you've gone into opening this issue. I believe that what's going on here is that `offset` doesn't work properly...

@ghenania thanks for the data. I will look into the cause. For the time being does the problem get resolved if you use a smaller value for `accuracy` ? For...

I am planning on improving the performance impact of increased accuracy by using the Bezier Clipping algorithm for intersections. One thing you will also find is that the API runs...

@ghenania I looked at the test data you sent me and created a unit test with it, but I haven't been able to introduce a good fix. The data presents...

@ghenania I still plan to improve this issue but it's non-trivial. I did a deep dive with your test data and I didn't see areas the performance could be improved...

@ghenania You might try pre-processing the paths by converting them to series of line segments. The advantage here is that line-line intersection is O(1) for very-high accuracy and BezierKit has...

@edudnyk I would definitely be interested in what you came up with! Getting the PR accepted into the codebase would be a bit of a higher bar though. It'd need...

Hello. Thanks for the example. It looks like this is a problem in `BezierCurve.outline(distance:)`. I'll fix that. As a workaround I'd suggest checking if all the points in the curve...

@typoland the `BezierCurve` type doesn't have a `cgPath` property but `Path` does, so you can do `Path(curve: ...).cgPath` instead.