PartDesign Hole feature

[NormandC]

I'm rebasing regularily on my computer, so it's still in good shape

Awesome.

[wmayer]

Since there are further requests to finally add this to master I gave it a try yesterday evening. However, due to the latest changes some things have been broken and in the that stage it doesn't work any more. So, I found and fixed a couple of issues but it still has some problems.

I have pushed the rebased and fixed branch to my github repo: https://github.com/wwmayer/FreeCAD/commits/hole

• The FeatureHole replaced Length with Depth but in the command still Length was used
• When canceling the command abortCommand() is invoked to revert all pending changes of the document. Therefore the member variable vp is set to nullptr which wasn't handled.
• The boost connection wasn't disconnected in the destructor which then caused crashes when using the command more than once
• pass double values instead of quantities to doCommand

At the moment things basically work again but there is a nasty issue I wasn't able to figure out: when double-clicking the hole feature after creation it correctly shows the values. But when pressing OK then diameter and hole cut type always changes their values.

Nevertheless, I think it's again in a state that it can be merged to master now. This way we also get a wider audience that may report more bugs.

[eivindkvedalen]

Since there are further requests to finally add this to master I gave it a try yesterday evening. However, due to the latest changes some things have been broken and in the that stage it doesn't work any more. So, I found and fixed a couple of issues but it still has some problems.

I have pushed the rebased and fixed branch to my github repo: https://github.com/wwmayer/FreeCAD/commits/hole

• The FeatureHole replaced Length with Depth but in the command still Length was used
• When canceling the command abortCommand() is invoked to revert all pending changes of the document. Therefore the member variable vp is set to nullptr which wasn't handled.
• The boost connection wasn't disconnected in the destructor which then caused crashes when using the command more than once
• pass double values instead of quantities to doCommand

At the moment things basically work again but there is a nasty issue I wasn't able to figure out: when double-clicking the hole feature after creation it correctly shows the values. But when pressing OK then diameter and hole cut type always changes their values.

Nevertheless, I think it's again in a state that it can be merged to master now. This way we also get a wider audience that may report more bugs.

Thank you for working on this. I've also done lots of changes locally, and I'll try to incorporate your changes when necessary. Please don't merge the current version, I'd like to get some more functionality in first... I'll push my changes to github during the next days, so more people can test.

Eivind

[wmayer]

Thank you for working on this. I've also done lots of changes locally, and I'll try to incorporate your changes when necessary. Please don't merge the current version, I'd like to get some more functionality in first... I'll push my changes to github during the next days, so more people can test.

OK. Please note that since posting on this thread I pushed a few more changes to fix a build error with older OCC versions and a couple of warnings.

[chrisb]

Thank you for working on this. I've also done lots of changes locally, and I'll try to incorporate your changes when necessary. Please don't merge the current version, I'd like to get some more functionality in first... I'll push my changes to github during the next days, so more people can test.
Eivind

May I gently ask for the state of the hole feature? We talked about it and could fairly well use it in the Path Workbench.

[HoWil]

May I gently ask for the state of the hole feature? We talked about it and could fairly well use it in the Path Workbench.

+1... very interested.
BR Howil

[eivindkvedalen]

May I gently ask for the state of the hole feature? We talked about it and could fairly well use it in the Path Workbench.

I've had too much other work lately to finish this. I also wanted to add actual threads to it (I've got a 3D printer at work), and that has been more difficult than I anticipated. Additionally, I have had trouble running FreeCAD in a debugger here (Ubuntu 17), as it takes ages to both start and step through code. That makes development very tedious and time consuming. Now it is almost vacation time, so I might get some more time. I might also end up with splitting this into two phases, with real threads postponed.

Eivind

[chrisb]

Looking forward for it. It's done when it's done.

[NormandC]

I might also end up with splitting this into two phases, with real threads postponed.

That would be a reasonable course of action IMHO.

Have a nice vacation!

[peterl94]

I might also end up with splitting this into two phases, with real threads postponed

Seems like the use cases for modeled threads are fairly limited anyway. In the CAD software I'm familiar with, modeled threads (internal and external) are created with a separate thread feature.