As every page is contained in the same QScrollArea we must ensure that
after page is changed the scrolled area is scrolled back to top-left
corner.
Fixes: #11981
Issue 8064 occurs when FreeCAD passes a Voronoi diagram to
Boost that becomes self-intersecting when Boost truncates the
diagram's coordinates to integers. This occurs when the discretizer
slightly misses closing the polygon generated for the letter by less
that FreeCAD's epsilon, then the wrapping Python code closes the
polygon by adding the initial polygon point as the final point.
This creates a short segment that, depending on the position of
the letter in the coordinate system, may end up being moved one
Boost coordinate delta away from the intended point, which can
end up self-intersecting.
Since the miss is very small, FreeCAD should treat it as it it
were the initial point. There's no need for a duplicate copy of
the initial point, so we remove this point close to the initial
point and let insert_many_wires() close the polygon as usual.
The function would trigger the creation of duplicate Draft Polar Arrays (only on Linux and only if the Fuse option is selected and the Link Array option deselected).
Forum topic:
https://forum.freecad.org/viewtopic.php?t=84090
The reapply_diffuse_color function is no longer required anyway as Issue #8340 has been fixed.
Eliminate m_measurement_inch to clean up logic for priority of MEASUREMENT and INSUNITS.
Save the actual scaling factor rather than the scaling enum so a switch statement is not executed for each call to mm()
Add to CDxfRead the work to handle dxfScaling option, ImpExpDxfRead just has to set it up now.
Get the scaling factor from a lookup table rather than a switch statement
Display a message explaining what the scaling factor is and where it comes from
Remove large amount of Lint.
* Update CI_cleanup.yml
The release of upload-artifact@v4 and download-artifact@v4 are major changes to the backend architecture of Artifacts. They have numerous performance and behavioral improvements.
* Update sub_buildMacOSCondaApple.yml
update artifact to v4
Update sub_buildMacOSCondaIntel.yml
updated artifact to v4
Update sub_buildUbuntu2004.yml
updated artifact to v4
Update sub_buildUbuntu2204Conda.yml
updated artifact to v4
Update sub_buildWindows.yml
updated artifact to v4
Update sub_buildWindowsConda.yml
Update sub_lint.yml
updated artifact to v4
Update sub_wrapup.yml
update artifact to v4
Update sub_prepare.yml
updated artifact to v4
* Update CI_cleanup.yml
The release of upload-artifact@v4 and download-artifact@v4 are major changes to the backend architecture of Artifacts. They have numerous performance and behavioral improvements.
Update sub_buildMacOSCondaApple.yml
update artifact to v4
Update sub_buildMacOSCondaIntel.yml
updated artifact to v4
Update sub_buildUbuntu2004.yml
updated artifact to v4
Update sub_buildUbuntu2204Conda.yml
updated artifact to v4
Update sub_buildWindows.yml
updated artifact to v4
Update sub_buildWindowsConda.yml
Update sub_lint.yml
updated artifact to v4
Update sub_wrapup.yml
update artifact to v4
Update sub_prepare.yml
updated artifact to v4
* Cleanup and switch to using MakePipe
* Cleanup unused include
* Use Frenet mode in building pipe
* Restore original code, add a control property
* Hide property, and init on new objects
* Restore prior behavior for legacy objects
* Clean up git blame; add missing move to keep helix same with new makePipe call
* Remove debug include
* Use doxygen syntax for deprecation comment
* Add unit tests; restore code for angled helixes; optimize zero angle helixes
* Lower test precision to accept platform variations
* Loosen more
* Correct restoration
* Tweak test volumes to match restored helix creation
* Restore helix generation parameter
* Fix test; delint
This PR makes the selection of the cutting object more flexible. It can be a face, an edge or an object with a single subelement of that type. Any planar object can also be selected. This PR makes the Arch_CutLine command superfluous. It was therefore removed.
Fixes a problem introduced with a previous PR of mine (#7591). Hosts would only be touched if that property of the window was modified. But the hosts of a window should also update if other properties of the window change.
Additionally a width or height change of a window now touches the hosts on the subsequent shape change.
