Although it is not entirely sure yet, we are fairly certain that libArachne release will have
a setting version of 18, so it is changed by this commit. With this change, the VersionUpgrader
will be properly triggered.
Contributes to CURA-7683 and CURA-7656
We have a change now that requires a version upgrade. This triggers all profiles to update for the user, and we must update accordingly in the built-in profiles.
Contributes to issue CURA-7118.
Unsure whether this is necessary, but we decided to do this to make
the evaluation logically equivalent to the existing code currently
in master.
CURA-6711
In profiles that overwrite the support infill density, also keep it 0% for tree support.
Except PVA profiles. Those are probably better off with their normal infill density.
Fixes#5297.
Conflicts:
resources/quality/ultimaker2_plus/um2p_pp_0.8_draft.inst.cfg -> Weights being changed while a whole slew of fixes were being done on 4.0
resources/quality/ultimaker2_plus/um2p_pp_0.8_verydraft.inst.cfg -> Ditto
This reverts commit 9432252de472c76ef5b7df954d4cb18aefc9fff7. It was assuming the wrong default speed_print value of 60. It's not always 60. We need to find a different solution or modify the script.
Reverts the fix for issue CURA-5342.
- Add a new field "variant" in "metadata" section for quality profiles.
"material" will only contain values such as "generic_abs", and
"variant" will contain values such as "0.25 mm", "AA 0.4", etc.
- Reformat "metadata" section to have the following order:
- setting_version
- type
- quality_type
- weight
- global_quality
- material
- variant
CURA-4451
- Add upgrade script for 3.0. to 3.1
- Upgrade old stack files so they will use "empty_quality" as the
"Not Supported" quality profile.
- Increase SettingVersion to 4
These are now upgraded to version 3, meaning that they will have to increase their version numbers and remove any start_layers_at_same_position settings they define. None of these profiles define any start_layers_at_same_position so it's just the version number then.
Contributes to issue CURA-3479.
Otherwise you get cryptic error messages about settings that may be hidden having invalid values, since minimum fan speed may not be higher than maximum fan speed. The value of the setting with the default settings should be the same.
Contributes to Github issue #1268.
