Fixed detection of config data at the end of gcode files
G-code as config file was not imported correctly because end of windows
stile end of lines (CRLF) were not processed correctly.
See the file at #8172
on PrusaSlicer too early now on some newest platforms, where the
application is not yet fully initialized. This fix postpones loading of
files in that case.
There was a bug in wxWidgets 3.1.4. (wxWidgets/wxWidgets#18998)
So, we cherry-picked fixing commit from the upstream wxWidgets to our "v3.1.4-patched"
Note: It's update of the Sha256 for wxWidgets in master branch
* Fix for #8024 - Wrong translation (German)
+ Translated phrases from wxWidgets localization are added to zh_CH dictionary
+ Updated MO-files for DE and zh_CH dictionaries
Suppress the G-code find / replace substitutions for the non-G-code
sections (comment blocks) at the start and at the end of the G-code file.
This commit extends the suppressed blocks for G-code find / replace
to placeholders for initial / final M73 commands and over the trailing
G-code comments.
Fixes gcode substitution: replacing comments removes initial and final M73 commands
Disabled check for "G92 E0" in layer change G-code for other firmware types
than Marlin 2 and Marlin Legacy. We don't know whether other firmware
flavors are sensitive to E axis accumulation error and we know that
RepRapFirmware is not.
Fixes#7846
+ Changed a script of the merging new POT with existing PO files.
Now it processes just a PO-files which are provided by community.
Community PO-files are updated from the new POT
Steps to repro of a bug:
1. FFF/SLA printer is selected
2. Load 3mf projet with SLA/FFF printer
3. Chnage printer to the FFF/SLA
=> (Print a Filanemt Settings)/(Print a Materials Settings) are disabled
Notes: This issue appeared after https://github.com/prusa3d/PrusaSlicer/commit/bfce4f6, when find_toplevel_parent(plater) instead of plater was set as a parent for ProgressDialogs
The main contribution of the smooth_outward function for multi-material segmentation was the removal of duplicate points in polygons using MutablePolygon::remove_duplicates().
But the issue with this function is that it deletes points only based on their distances, which could cause problems like in #7838.
