from the background slicing thread, that supports cancellation.
The generic mechanism is used for generating thumbnails into G-code and
Fixes Fix deadlock when canceling the slicing while gcode is creating thumbnails #6476
Thanks @supermerill for pointing out the issue.
* first_layer_extrusion_width moved from print to object supermerill/SuperSlicer#1225
* now unset skirt width will only use the first layer width if it's one layer high
instead of excluding overhang from "bridged" tag and making exceptions to use overhangs alongside bridges,
now revert back to when overhangs are bridge and make a unique exception to not apply bridge acceleration to them.
- now a setting can be "phony"
- a phony setting isn't saved in a config file
- a phony setting should be computed from other settings
- change/add colors, icons, and callbacks (in PrintConfig.cpp) to make phony settings works
* fix m_last_too_small fusion test
* now use a modified douglas_peucker to take into account the segment length instead of the tolerance only
* some tooltip & default value change for resolution.
The problem is that PrintObject support generator is only run when m_layers.size() > 1, so one-layer object will skip it.
It apparently never worked, after recent refactoring (probably 8bfc986) it started to crash in GCode generator.
This commit fixes the crash, but not the problem. The raft is still not generated (like in all versions since 2.0.0 at least).
above the solid infill. Should fix
first layer of vase (after bottom layers) is bulging (0.6nozzle, 0.4 layerhight) #3712
Adjust flow of the "second" layer in spiral vase mode #2795
The thread local storage variables for the random number generator
were replaced by an external context variable.
Thread local storage is a scarce resource.
It can go lower than 0.0125 for the perimeters.
It's kept at a minimum of 0.0125 for infill & thinwalls/gapfaill for performance reasons
and to avoid too much artifacts / corners case.
1) The macro-processor sanitizes the source code line for invalid UTF-8
characters. Ideally these invalid characters would be replaced with ?,
they are just dropped as of now. Better than showing an empty string
when converting to wxString though.
2) G-code export collects full error message for 1st occurence of an error
for each custom G-code block.
3) The composite error message now displays the errors collected in 2).
4) The error window is now scaled bigger and the Slicer logo is smaller
if the text is to be rendered with monospaced font, as the monospaced
text will not be word wrapped.
Errors in the file output templates are reported in mono-spaced font,
so that the arrow character ^ is displayed at the right column
pointing to the offending spot.
