The speeds are not in the tool library on purpose, because they depend more on the material than on the tool itself. If you always work with the same material than yes, it would make a lot of sense to just add the feeds into the library. What you want to do is probably supported by the Job Template....

It should be possible to merge the operations together so the code manages the choice between faces and edges depending on the users selection, like many other tools. IMO it doesn't make sense this being two seperate operations and as we add operations to path the toolbars may become cluttered. See...

That's hard to say, depends on your branch and when you pulled/fetched the last time. What I do is fetch the latest changes to freecad, then swtich to a new branch based on freecad/master. I build out of source so I delete the build directory and create a new build. I don't know enough about cmake a...

The blank lines I don't know, but the additional end tag doesn't look like valid XML to me. Not an expert though.

From your output above your tool table seems to be empty and the TableName is a regular string. I would probably suggest removing your configuration files, I have the feeling that something else in the config file got out of whack and it's spilling into the tool table.

Again this highlights the need for basic testing on a python2 build. Folks messing with code using only python3 are breaking stuff. As vocx already said, those days are gone. IMHO there is really no point in doing anything for py2 or qt4 in the 0.19 development. The major focus for 0.18 was to beco...

haha - relax, it wasn't you. And it's not about the specific issue, it's a general call to not trip somebody who's already using Path You're too funny.

I've just been chasing my tail for an hour because of a change in default behaviour. I probably missed the discussion but we cannot expect that all Users check this forum regularly and keep up with whatever we're currently cooking. So if you make a change, add a feature, or take one away - please ma...

wmayer wrote: ↑

Thu Oct 03, 2019 8:22 am

I fixed the build failure because of the missing export macro and pch in the source file. But I didn't realize the PCH inside the header and had no build failure because of this.

Thanks, I didn't know about the export maccro and have made a note of that, and the PCH guidelines.