This is a considerable diversion from the current UX status quo and I was wondering where it comes from. The legend is displayed in the tooltip of the entry field, as it is for all other fields. Why we would want to add the legend for the "Output File" and not - for instance - for "Arguments", or th...

Those are actually the same thing, the library editor is where the tool table is defined. Not claiming that the naming convention is great, or even consistent - just providing some background. Personally I'm OK with either name.

Giulio Buccini wrote: ↑

Fri Feb 14, 2020 1:13 am

This is the best I can get when trying to mill the little platform (mill command: "profil based on edges"):

which version are you using? and can you upload your file?

Great page - are you looking for a review or for content?
If it's the latter, do you have an outline of what should go there?

I have a class in C++, let's call it A. A has a member function which returns objects of class B. 'thing is, B has a pointer to A. I know how to wrap A and all its members into a python class, APy - and I know how to wrap B into BPy. But what I can't figure out is how to add a reference from BPy to ...

freman wrote: ↑

Wed Feb 05, 2020 1:36 am

adding feedrates to this line in PathDressupPathBoundary.py seems to fix the missing feedrates on G2 paths:

Code: Select all

  commands.extend(PathGeom.cmdsForEdge(edge, flip, False,50,tc.HorizFeed.Value,tc.VertFeed.Value)) # add missing HorizFeed

what if the edge is horizontal?

I have a provisional mod which applies that strategy and seems to fix the tool crash problem. Any comment of suitability of this approach? Yes, the dressup does what you told it to do. If you limit the height below the safe/clearance hight it's your own doing. And it does correctly limit all moves ...

I have located the offending line in PathDressupPathBoundary.py pos = cmd.Placement.Base ### this is causing spurious tool-crashing path. That is certainly not the problem. The problem is that you have restricted the z-axis of the BoundaryDressup to be below your safe/clearance height.

Russ4262 wrote: ↑

Tue Feb 04, 2020 2:38 am

If the FinalDepth is set below the bottom of the hole, then a warning will be issued in the report view.

TBH I never understood the reason behind this warning. In almost all cases drilling goes beyond the bottom of the hole, otherwise you won't get the entire hole.

DeepSOIC wrote: ↑

Tue Feb 04, 2020 12:40 am

mlampert wrote: ↑

Tue Feb 04, 2020 12:17 am

parameterAt is not used anywhere.

Have you searched all addon/macro code too? because I already found one:
https://github.com/luzpaz/SlopedPlanesM ... Py.py#L696

Good call - I did not. Does that mean we can't change the API?