Sorry for the long radio silence; going through a rough time right now and limited time for hobbies.

I tried my best to create a PR with the generator and the test. Feedback welcome (and most likely necessary )!

sliptonic wrote: ↑Mon Jan 31, 2022 3:11 pm Great! Here to help, if I can so don't be afraid to ask.

Thanks a lot for the explanations. This is very helpful. I most likely will need a bit of time to work through the magic world of github and will try to submit a PR.

I found some more time over the weekend to try my hands on the code with limited success and would appreciate help with a few questions. I am really not a developer and therefore might run into issues that sound almost trivial to others. Development setup Before jumping into some question about the ...

I have to admit that I don't yet fully understand the structure of the code. Path[Operation]Gui - Pretty clear to load the Gui panel and manage the Gui. If we follow the simple logic in the last post the user only has to select the arcs, select the toolbit and the coolant. The call of the Generator ...

Identifying the start and the end point is surprisingly simple by selecting the arc at the bottom of a properly modeled keyhole: import FreeCAD from PathScripts.PathUtils import loopdetect doc = FreeCAD.ActiveDocument obj = doc.getObject("Pocket001") elt = doc.getObject("Pocket001&quo...

Do the keyhole cutters have a cutting edge on the top of the wide part? No. Only on the bottom; so they can't cut themself free. Scriptability is absolutely the goal. We want as much of Path to reusable to macros and also external scripts as possible. But we're working in 'baby steps'. Reusing comp...

All my comments are predicated on the idea that a keyhole is a super simple cut as described. I could be convinced that the input geometry should be a wire and the logic is to follow the wire from start to end and then reverse it with rapid moves to exit. That would work as well and would let you d...

The generator has nothing to do with the user selection. That's all going to be handled in the GUI and operation code. Looking at your example, you take the input face and immediately calculate a startPoint from its center of mass. Why not just take the startPoint and let the operation calculate th...

Find attached a first crack at the generator and the respective test file. I deviated from sliptonic's logic of having a start point and an end point for two reasons: (1) This would prevent us from defining multiple keyholes in one go. I would find it more convenient to select multiple holes and the...

sliptonic wrote: ↑Tue Jan 18, 2022 8:36 pm Start with step one. I'll help as needed.

Thanks a lot for the explanation. Let me dig into this over the weekend!