- when an error occurred during the Write process, the Edit button must not be enabled
In this case the machine state is still at femsolver.run.PREPARE. If no error occurred it went one step up.
Replace the "add_parameters" routine by an array of individual
functions (one for each parameter letter) and a simple piece of
code that calls the appropriate parameter passing functions in
the specified parameter order. Some of the parameter letters
can share the same parameter passing function in the default
configuration.
This not only simplifies the code but opens up the possibility
of replacing the code processing a given parameter letter
("Q", for example) with new code in the postprocessor file
without having to modify the shared postprocessor functionality
(in the three Util*.py files).
- a typical use-case is to open a document with an existing cut and only this cut is visible. When now opening the section cutting tool, the user got the fault message that there were no visible objects to be cut.
- the transparency for the cut was not explicitly set. Therefore the default transparency for new objects was used instead of the transparency of the objects to be cut.
- workaround for a graphics issue: when cutting objects intersection each other (only then), the transparency setting might be ignored. The fix is simply to change the default color slightly (By the way, this issue is independent on the color that is set in the Part preferences as color for new objects, seems to be a graphics driver or OCC issue.)
- besides this, avoid code duplication by using a lambda function
- the type change fixes this error: \src\Mod\Sketcher\App\planegcs\Constraints.cpp(509,54): warning C4267: '=': conversion from 'size_t' to 'unsigned int', possible loss of data
- the scone change removes a non-existing definition
The original implementation always took 150% of the addendum/dedendum
difference as fillet radius. For a standard full-depth system this
results in a normalized value 0f 0.375, which is pretty close to the 0.38
definded by the basic ISO rack. However, when using much shorter teeth as
e.g. required for a splined shaft, the fillet becomes way too large.
In addition, I don't understand the approximation to calculate the
distance between the gear's center and the top of the fillet yet. It was
only refactored to allow the custom fillet radii, but it retuns the same
values as the original implementation.
However, with high pressure angles, up to 45° used for splines, this
approximation comes to its limits.
