notification with some locales, we don't want PrusaSlicer 2.3.0/2.3.1
to show this notification. On the other hand, we would like PrusaSlicer
2.3.2 to show an update notification of the upcoming PrusaSlicer 2.4.0.
Thus we will let PrusaSlicer 2.3.2 and couple of follow-up versions
to download the version number from an alternate file until
the PrusaSlicer 2.3.0/2.3.1 are phased out, then we will revert to
the original name.
Cherry-pick of 2e55898d78ddca4753adb60c9222c52bc9ee8ba8
Fix of an extremely slow bridging calculation, caused by an extremely
slow bridged area detection function, of which the results were never used.
Fixes "slicing fails or takes too long #5974"
that configuration could be recovered in the case PrusaSlicer.ini
is corrupted during saving. The config is first written into a temp file
marked with a MD5 checksum. Once the file is saved, it is
copied to a backup file first, then moved to PrusaSlicer.ini.
When loading PrusaSlicer.ini fails, the backup file will be loaded
instead, however only if its MD5 checksum is valid.
The following "Fixes" comments are for github triggers. We implemented
a workaround, not a fix, we don't actually know how the data corruption
happens and why. Most likely the "Move file" Windows API is not atomic
and if PrusaSlicer crashes on another thread while moving the file,
PrusaSlicer.ini will only be partially saved, with the rest of the file
filled with nulls. We did not "fix" the issue, we just hope that our
workaround will help in majority of cases.
Fixes prusaslicer wont open 2.3 windows 10 #5812
Fixes Won't Open - Windows 10 #4915
Fixes PrusaSlicer Crashes upon opening with "'=' character not found in
line error" #2438
Fixes Fails to open on blank slic3r.ini %user%\AppData\Roaming\Slic3rPE
just M600, reset the internal retract counter, so that a retract
will happen after the firmware returns from M600 to the initial position.
Fixes "Blobs on print after manual color change #6362"
Fix of an extremely slow bridging calculation, caused by an extremely
slow bridged area detection function, of which the results were never used.
Fixes "slicing fails or takes too long #5974"
just M600, reset the internal retract counter, so that a retract
will happen after the firmware returns from M600 to the initial position.
Fixes "Blobs on print after manual color change #6362"
fix crash (comes from commit 0a65e1b0d6a234bb9c9d58047940bed85260d700)
fix slicing preview
also fix a toolchange missing (just notifying the writer)
supermerill/SuperSlicer#1347
- now only extrusions with a "0" are taken into account for autospeed computation
- removed min_mm3_per_mm from extrusionentity as it's now computed by a visitor.
- ironing pattern now use ironing role like ironing PP
- ironing_speed is now a float or percent, over top_solid_infill_speed
- added some missing ratio_over
- updated to_prusa to convert % accel & speed to flat value from config, instead of 0.
* Raft -> Radeau
* Traduction des fichiers HTML de calibration
* Mise en phase des fichiers HTML et de la traduction francaise*
Simplification sur certains paramètres
* Éviter de croiser les périmètres - Longueur de détour maximum
* Longueur de détour maximum ( rappel Éviter de croiser les périmètres)
* Seulement pour le côté intérieur
* le côté extérieur (se comprend très bien sans seulement)
Fixing model import of models with nearly degenerate triangles, which
degenerate after transformation (translation or rotation).
There was certainly a bug in PrusaSlicer, however this bug was triggered
mostly by the ASCII STL files generated by OpenSCAD, likely due to insufficient
number of decimal digits when saving an ASCII STL, see
[openscad/openscad] STL export should contain single precision floats (#2651)
