Could you give me a bit more information and a test case. Pictures would be great.

Wow, I already entered a ticket and forgot about it.

https://www.freecadweb.org/tracker/view.php?id=3464

You're not missing anything. The gcode import + pre-processor is very early Path stuff and hasn't been updated to use the Job structure. As you noted, it creates the path object outside the job tree and it can't be moved inside. I'll add a mantis ticket for this. A Custom is an empty operation that ...

Got it. Thanks.
It won't leave any uncut material but I understand why the retract is triggered.

realthunder wrote: ↑Mon Aug 06, 2018 4:00 am
BTW, there are still many retractions here, because your stepover of 85% is too big, assuming the tool shape is circular. You'll have left overs at the corners.

Not clear. why does this result in extra retractions?

Yea, I read that above and I remember the discussion well. This behavior is necessary to support mill face or any op where the cutter can't directly plunge. It took me a while to understand why it's applicable here. After all, the start of the first pocket is perfect. It works just as it should eith...

I'm trying to play catch-up here. Bear with me but it looks like the real problem is how it's handling two separate pockets. I tried setting the operation as Realthunder suggested (70% stepover, keeptooldown=True, No start-point passed) and I still see the collision when it transitions to the second...

Amazing work! I'm curious about the user use of pyclipper. I've not used this library before. However, Angus Johnson's clipper lib is the basis of libarea/PathArea which underlies all of our current 2D operations. I would encourage you to chat with @realthunder about extending PathArea rather than s...

An update: As of August 2018 both Openvoronoi and OpenCamLib are licensed LGPL