_n

Thanks,
Justin

We’re doing a big collaborative art project with alot CNC plywood work. The vector files that artists submit have to be prepped for the CNC machine and Offset Path is a necessity. The resulting files have been giving the CAM software fits because of the bug, and your java-script literally saved me tens to hundreds of hours of cleanup at a time when I cant afford it.

Thank you so much!

-jonny

Right now the script keeps only the leading point (lowest index on the path) and copies the direction handle from the trailing point to that leading point. This works fairly well so long as the points are reasonably close together, but as the example above shows, it leads to distortions as the distance between the first and last point grows relative to the overall path geometry. After reading Nathaniel’s writeup, and looking at the referred link to Douglas-Peucker, I’d say that the script could pretty easily be adapted to use such an algorithm as an alternative. I’ll see if I can’t find some time to try to code that in (warning, however, my April has some deadlines, so it might be a bit).

I have already made some more modifications to the script and can release a 1.4 version very soon. I just didn’t want to change it just as Nathaniel was reviewing it, and people were trying it out (in case heaven forbid I add a bad bug Here are the highlights

I added options to control position of remaining point on removal. The new choices are to keep the leading or trailing point, or to average the position of the points. I also fixed bugs in docGetSelectedPaths(). CompoundPathItem objects don’t seem to to have properly formed pathItems arrays when they contain what appear to be groups of paths, so when certain compound path objects were selected, no paths were found.

One last note, older versions of the script are available at the wiki by clicking on the file link and selecting the link for the date/time of an earlier version, which will download that version.

Enjoy,

-Jim