* fix: Spreadsheet applies alias even when focus lost
The original stylesheet behavior was that the alias or content fields
could be edited, but only after enter was pressed the field would
actually update. This change makes the field apply when focus is lost
on top of when enter is pressed. This makes it easier to enter the
alias of a lot of fields at once.
A regression from #9506 where `self.multiply` was removed but not all references to it were updated.
I'm not a Python guy but from what I can see the behaviour is the same - `offsetvector` is still an `App.Vector` which `self.multiply` used to use as well.
Tested with a project that previously didn't work, and now shows a nice `Arc`-type dressup in a circular pocket.
This is a rename that got missed in #6637. I ran into this bug when trying to post a job using the `linuxcnc` post processor on a Windows 11 machine, running the weekly build titled `FreeCAD_weekly-builds-33576-2023-07-13-conda-Windows-x86_64-py310.7z`.
Minor modifications to make it compile with previous refactorings.
The only substantial change to the original is moving the
getElementHistory function from ComplexGeoData to MappedName so
that the dehash function can remain private.
- deleting a dvp will now delete any hatches, dimensions or
balloons belonging to it.
- deleting a dvp that is the base view for a section or detail
is still blocked.
The load of the current file in test_open_head is fine, but
open_de9b3fb438 goes into an OOM even in huge (e.g. 10GB) systemd.
This probably needs a proper fix by upstream in regard to the migration
modules that load the old code, but until then (since the rest works on s390x)
this unblocks the package self-test in Debian & Ubuntu.
Patch by Christian Ehrhardt <christian.ehrhardt@canonical.com>.
This is Debian bug https://bugs.debian.org/984952 and Ubuntu bug
https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1918474.
Been part of the Debian edition of FreeCAD since 2021.
While working on https://github.com/FreeCAD/FreeCAD/pull/9867 I noticed my patch
showed up with a lot of linting issues in code I did not touch, to a point
where the view was very cluttered by lintian issues. Here is my second
try to reduce the number of issues discovered by the linter. Some
issues are still left, as I fail to see how to sensibly reduce the number of
parameters or local variable used.
The issue only happen when splitting jobs on tools (orderby == Tool), and when
USE_TLO was active and the preamble include G49. The first move is then done
before tool height is set, and can cause damage if the existing tool height is set
to more than the gap between the spindle and the table or work piece, when the machine
take a sudden dive straight down.
Removed move between G49 and first G43, to ensure all moves are done after G43
correctly set tool height compensation.
Rewrote code to introduce new method fixtureSetup() to ensure all orderby alternatives
behave the same way.
Fixes#9866.
