Optimized and Added New Features to the HoneyCombSolid Macro

[eoyilmaz]

Thank you for creating a pull request to contribute to FreeCAD-macros! To integrate your macro please make sure the following steps are complete:

• [X] Please check this box if you're not submitting a new macro.
• [ ] Are you submitting a new macro ?
• [x] Have you followed the 'How to submit a macro' section of the README.md ?
• [x] Your macro has a Description in its header.
• [x] Your macro has a CamelCase name.
• [x] Your macro is named appropriately.
• [x] Your macro contains a Metadata section that immediately follows the header description.
• [x] Your macro is Python3/Qt5 compliant and tested on the latest FreeCAD stable and development releases.
• [ ] You're including documentation on how your macro works (bonus: screenshots and/or video on the Wiki)
• [x] Commit message is well-written
• [ ] Commit message is titled in the following way [MacroName] Short description.
• [ ] Optional, write or update the changelog in the macro, from latest to oldest.

And please remember to update the Wiki with the features added or changed once this PR is merged.
Note: If you don't have wiki access, then please mention your contribution on the 0.19 Changelog Forum Thread.

---

Hi this is an update to the HoneyCombSolid Macro. I have done fixes to the general approach, added new features and optimized the code.

• Fixes:
  • For very big sizes the old code was not generating proper geometry.
• New Features:
  • The old approach was doing an unnecessary boolean operation and it was not possible to only get the hexagonal shapes:
  • The old one forces the user to generate an unnecessarily big hexagon grid if the user requires a custom outline. New approach allows the hexagon shapes to be combined with a custom shape.
  • This approach eliminates the unnecessary boolean operation and makes it work 4.5-5x faster.
  • The user can specify the usage of the container geometry with the UseContainer parameter.
  • The user can still switch back to the old algorithm by setting the UseNewAlgorithm parameter to False:
• Optimizations:
  • As explained above not using a container is 4.5x to 5x faster:
  • And the new algorithm is 20% faster if a container is used:
  • The output matches the previous approach:

[galou]

@christiangda Do you agree with the changes? They look good to me.

[christiangda]

@christiangda Do you agree with the changes? They look good to me.

totally agree, thanks