The GUI tools for moving the model just adjust the placement property of the model clone. You can always adjust that placement manually in the property pane, including the Z position.

secondly: selecting a peck cycle in the UI disables the dwell option. These should not be mutually exclusive. A dwell time is also an option for a peck drilling cycle. Not true. LinuxCNC and other controls don't support dwell on a G83 which is why we disable it. Some controls do support it but it's...

...the need to slow down certain parts of a path is another. I'm not going to claim to be an expert but based on my understanding this is a red herring. It's a hack. Simply slowing the feed rate, especially as a ratio of the existing feed rate is missing the point. Feed rate, spindle speed, and cut...

I recognize that there is an unmet need being expressed here. I'm certainly not opposed to adding a feature but I don't like this particular implementation. (no offense to 'The Russ' who is indeed a rock-star :D) In Path you control tool feed/speed through tool controllers. Both spindle speed and fe...

I sent a PR https://github.com/FreeCAD/FreeCAD/pull/3687. If you don't want to wait for it to get merged, it's a simple one-line change that just un-hides the interpsurface property. To use it, you'll need to somehow model the curve you want. I get weird results with a complete cylinder but somethin...

I'm excited to see this post. I've been looking at implementing something like a setup report. I wrote up some notes in the Path Development Roadmap in the multi job context section Being able to incorporate a views like this is definitely on my mind. I have some additional thoughts about how to int...

This should be pretty easy to implement. The way the dressup works is to take the probe input data, construct a surface and then use the surface to bilinear interpolate the gcode points. It should be easy to just make the dressup take an existing surface and use that instead. So you could model the ...

These are legitimate issues but I wouldn't expect a fast response. We have so many fish to fry (both large and small) that this level of optimization is likely going to have to wait. If course, if it's scratching someone enough, they'll itch it.

I believe we're limited to what opencamlib can do. I'm not aware of a way to break a recompute once opencamlib has been called.

There's 'cut pattern angle' available if you have cut pattern set to zigzag or line.