This reverts commit 6ff8537ff4fbd14ca09934cdb2bb987131a7b559. There is a non-trivial conflict
when merging to master, let's redo the commit after the merge so it is clear in history.
Make snap-shot to undo/redo stack only on release slider
Connected with attributes:
Text/advanced(char gap, line gap, boldness, skew ratio)
SVG(size)
Also change range for Boldness. VRT font-Ascent.
(different font may have different slider value range)
Fix line gap (it was denied when per glyph was false)
Check transformed bounding boxes of loaded objects instead of z_min of bounding boxes.
+ BoundingBox: added function shares_boundary() to detect if bounding boxes shares some boundary.
Fix for #11547 - .3mf files with similar sized components aren't being defined as multi-part objects
* Fixes SPE-2116. The reason for this bug was forgotten change in
WipeTowerIntegration after change in gcode.cpp.
* Prevents future similar bugs by unifing the functionality to a method.
1) Force OpenGL 3.2 as minimum required. If the graphic card does not support it, automatically switch to software renderer.
2) command line option: --opengl-version=X.Y -> allows to select core profile of version X.Y.
3) command line option: --opengl-compatibility -> allows to select compatibility profile of the highest OpenGL version supported by the graphic card.
4) command line option: --opengl-debug -> enable OpenGL debug output on card supporting OpenGL 4.3 or higher (output on console).
This bug was caused a wrong selection of the new added printer,
when some new vendor other then PrusaSlicer is added,
but PrusaSlicer has installed SLA printers.
(see SPE-2056)
* Replace the ramping travel with a smooth ramping travel.
* Replace helical layer changes with ramping layer changes.
* Implement the "lift before obstacle" feature.
Ignore the first intersection of the travel path with the object from which the travel starts.
Created a new class TravelObstacleTracker, for wrapping all data structures related to lift before obstacles.
During layer change, instead of generating the gcode, generate a placeholder tag. Then at the end of layer processing replace this tag with a ramping travel move.
This solves the issue, that one does not know the starting point of the current layer where the layer change gcode would be originally generate.
The ramping layer changes uses smoothing of the ramping travel. Also it is adjusted in such a way that it increases the ramp angle when the travel is too short, to always reach the next layer.
