This is necessary to ensure that all printers use a valid prime tower position, now that the position computation rule has changed and includes the base/brim.
CURA-10783
A lot was changed in support. The short of it is that we now think towers should be on by default, but aren't _completely_ certain about it. It makes more sense to do make this change before the beta rather than just before stable, so we have a chance to revert should it prove disastrous.
If this is set to an absolute value, the material settings wont have any effect anymore.
A much better way is to just set the default temperature, which is what the intent is
Should've done this in the merge, but I just increased the setting_version for these.
I also removed a deleted setting from the advanced visibility. We don't have tests that ensure that these visibility presets are good. Lucky I found it then, with a Ctrl+Shift+F search.
Previously, the ironing_inset was changed in the profiles to reflect
the changes made in the CuraEngine. This inset though was not taking
into account the ironing_pattern (in the CuraEngine, the inset is
compensated differently depending on the pattern).
This commit fixes that in the version upgrader and the printer
definitions in order to maintain the same behavior for the old
profiles.
CURA-7318
The slicer has been adjusted to give this setting a more logical function: It should be an inset of the outer edge of ironing as it appears in layer view where the lines are made thinner according to their flow.
As a result all of the slices with ironing have changed. This adjusts the setting value so that the actual slice output will not change, just the appearance of the setting.
Contributes to issue CURA-7318.
Conflicts:
resources/definitions/skriware_2.def.json -> File was rewritten while I modified the platform mesh. All indentation was changed to tabs which caused a merge conflict.
Conflicts:
resources/definitions/skriware_2.def.json -> On master the old setting value was changed to 'value' rather than 'default_value', while on this branch the value was changed to use the resolve function.
There's one that needed to be a 'value' to properly overwrite it. The rest are all about settings that were equal to the defaults anyway so I've removed those.
Contributes to issue CURA-6949.
