This `ns` fix might need further attention after testing. The section to which it pertains deals with optimizing rotations between ops with similar rotational axes.
Existing code to determine if shape volume indeed existed, failed.
Added additional pre-check for existing edges in shape to determine if shape geometry indeed exists.
In forum:
[Ticket #4411 - Can only generate pocket once for this shape, then it fails.](https://forum.freecadweb.org/viewtopic.php?style=3&f=15&t=49035).
There are a lof of scenarios where it's not possible to perform an operation without throwing an exception. Reporting an exception as error is not only annoying but often confusing because the user assumes he did something wrong.
So, for the moment many of these exceptions are reported as log messages but serious things like memory exception, std. C++ exceptions or unknown C++ exceptions are still reported as errors
there is no need to have 2 plugins doing the same
moreover FindProc does no longer work with recent Windows 10 versions, so it must be removed anyway
- configure.nsh: small code optimization
- Settings.nsh: update year
the translation folder was missing
- also add safe guards that really only the desired subfolders will be part of the installer not also files that may exist in the base folder
- Since realthunder's contributions some months ago, the 4 pattern features (mirror, linear, polar, mulitransform) can handle several features at once.
This PR allows to select multiple features when creating a pattern.
(This speeds up the workflow because at the moment one has to create the pattern with one feature and subsequently add more.)
- fix dialog issue that Add and Remove button could be active the same time
- use the keyboardTracking feature to avoid unnecessary recomputes (e.g. currently 3 recomputes when inserting "12.5" to the length field of linear pattern)
- fix wrong <extends> statement in .ui files (automatically spotted and fixed by Qt's Designer)
===========================================
In OCCT 7.4 (and apparently <= 7.4 too):
A GeomAdaptor_Curve obtained directly from BRepAdaptor_Curve will not work because it won't respect the
Location/orientation of the underlying curve.
This commit proposes to create a new GeomAdaptor_Curve from an intermediary curve handle to work around
this issue.
