* Start of new dogbone dressup
* Added Instruction and tangents support for G2/3 moves
* Added Maneuver class to represent a set of moves and process them coherently
* Created kinks and verify their creation.
* Added dogbone detection and verification
* Simplified gcode strings
* Added horizontal t-bones generation
* Added support for vertical t-bone
* Consolidated t-bone creation
* Added support for pathLength
* Added support for tbone on short edge
* Added support for long edges
* Added support for dogbones
* Fixed dogbone for non-horizontal lead-in
* Horizontal bone adaptive length tests
* Fixed dogbone angle and adaptive length
* Some code cleanup
* Added adaptive length tests for dogbones
* Split base data classes into their own PathLanguage module.
* Splitting dogboneII implementation into its constituents
* Moved adaptive length into DogbonII module
* Separate dogboneII generator test cases and changed interface to allow for dynamic length calculations
* Unit tests for length calculation
* Initial DogboneII unit test
* Unit tests and fixes for plunge move handling
* Unit tests for the remaining styles and incision strategies
* Basic DogboneII gui
* Added support for markers
* Better color and selection scheme for markers
* Cleaned up import statements
* Added DogboneII to Path WB init
* Support for dogbone on dogbone and fixed t-bone generation
* Fixed t-bone on short leg bones
* Fixed tbone on short edge when short edge is m1
* Fixed t-bone on long edge for m0/m1 and CW/CCW
* Removed redundant code
* Removed redundant 'Dress-up' from menu entries
* black code formatting
* added generator to cmake
* Fixed typos
* QApplication::setFallbackSessionManagementEnabled has been removed
* QString::medRef() has been removed. Use QString::mid() again.
* QTextStream::setCodec has been removed
* Use operator QVariant of the QFont class to make code Qt5 and Qt6 compatible
* Signature of QTreeWidget::mimeData() has changed in Qt6. Remove TreeWidget::mimeData() because it doesn't change the implementation
* QLayout::setMargin() is deprecated in Qt5 and has been removed in Qt6. Use QLayout::setContentsMargins()
* QDateTime::toTime_t() is deprecated in Qt5 and has been removed in Qt6. Use QDateTime::toSecsSinceEpoch()
* QDesktopWidget is deprecated in Qt5 and has been removed in Qt6. Use QScreen
Removes the BUILD_QT5 flag and adds a new FREECAD_QT_VERSION option,
which can be set to either "Auto" (default), 5, or 6. Auto detects which
version of Qt is installed on the system and chooses it. If both version
are installed, Qt5 is used.
Note that this DOES NOT implement compiling against Qt6, it only adds
the necessary cMake infrastructure to begin work on the source code
changes that will be required.
- add preview/live update to TaskSectionView & TaskComplexSection
- add view direction selector to uis
- use SectionNormal as Direction. Make Direction read-only
- simplify section line end point calculation
- section group command in toolbar
- make section and complex section icons consistent
- fix compsolid cutting tool
- terminology: single/piecewise to offset/aligned
- as discussed in https://github.com/FreeCAD/FreeCAD/pull/7642 the backwards compatibility for deprecated holes was already lost since FC 0.19
- this PR removes the deprecated types and transform holes created with FC 0.19 or 0.20 to the corresponding countersinks/counterbores.
- also add Counterdrill for translations
The counterbore is basically a special case of the countersink
with a countersink angle of 180 degrees and applied depth.
Handling it that way elimintaes some duplicate code and adds the ability to
combine countersinks and counterbore to form a counterdrill.
The sanity check on countersinkAngle can be safely dropped as it is ensured
by a constraint on the property itself.
HoleCutDepth is reset to 0 to force a recalculation of te depth when
HoleCutType is set to a new value.
But the line
pcHole->HoleCutCustomValues.setValue(false)
also forces a recalculation. So the depth was recalculated with the old
value in HoleCutType which was not expected behaviour.
================================================================
Master has a problem in that internal alignment constraints are suggested to the user for removal.
This is fundamentally wrong, as an internal alignment constraint are an inherent part of the geometry. They cannot be the ones suggested for removal.
The popularity contest algorithm is an heuristic algorithm that determines which redundant/conflicting constraints should be proposed for removal.
Basically, the algorithm works on groups of redundant/conflicting constraints detected via the QR decomposition. A constraint may belong to more than one group.
The algorithm runs some heuristics, each constraint scoring a value, the one constraint from each group scoring the highest is proposed (is more popular and wins the contest).
This PR documents the algorithm, and adds a further condition, that internal alignment constraints are never proposed.
As the solver works with solver constraints as opposed to the sketcher, which works with sketcher constraints, information about whether a solver constraint originated from a
sketcher constraint that is internal alignment is necessary. So the solver constraint is extended to accomodate this piece of information.
As a bonus, it fixes a bug. Solver constraints carry information of the ID of the corresponding sketcher constraint in their tag. Knots are not currently implemented as constraints.
However, the tag index was not being update. This caused the popularity contest to provide wrong suggestions despite good detection.
