* FEM: remove calculix from solvers
* FEM: remove calculix from joint with ccxtools if branches
* FEM: remove calculix from its if
* FEM: fix cxx typo in translations
* FEM: fix cxx typo in classes name
* FEM: fix ccx typo in shortcuts
* FEM: convert FEM_*CcxTools to CamelCase
* FEM: remove tests related to calculix
* FEM: remove test_solver_calculix.py from Fem/CMakeLists.txt
* FEM: convert all 'CalculiXccxTools' to 'CalculiXCcxTools'
* FEM: revert changes in all *_*.ts files
* FEM: convert 'SolverCcxtools' to 'SolverCcxTools'
* FEM: convert remaining 'Ccxtools' to 'CcxTools'
* Allow adding subfeatures to MultiTransform if there is no active Body
Previously the active Body would be checked and used to add new
subfeatures.
This would either do nothing, when no Body was active,
causing confusion for users becaues than can edit other features without
an active Body.
Or it would add the subfeature to the wrong Body if another Body than the
one of the MultiTransform was active.
Now the Body of the MultiTransform is checked and used.
# Conflicts:
# src/Mod/PartDesign/Gui/TaskMultiTransformParameters.cpp
* Change getTopTransformedObject() to protected
This needs to be called from the MultiTransform.
* Fix typo
The notifier string must be a std::string() instead of an empty C string as otherwise the wrong methods are called so
that all messages are sent to the void.
This regression was caused by commit 3795444df473651
If you have a mirror feature and set the mirror plane with the normal feature editing the recompute works. But if the mirror plane is set with the property editor then the recompute fails with the message that no mirror plane reference is set.
This is related to a an empty sub-name list of the link property instead of a single and empty sub-name element.
This PR allows to specify a sketch, plane or datum plane without a sub-name.
For more details see: https://forum.freecad.org/viewtopic.php?t=86568
This fixes#13238
and MeshGrid::CalculateGridLength(unsigned long, unsigned long)
For almost flat meshes CalculateGridLength may compute a grid with a huge amount of cells that allocates the whole RAM of the system while for an exactly flat mesh a grid with a sensible number of cells is computed.
Use the overloaded methods of MeshGrid::Rebuild(unsigned long) and MeshGrid::CalculateGridLength(unsigned long) instead
