I was mixing up the versions there. The new version needs to be 20, since 19 was already used for 4.13. We can't use 18 since that was reserved by the betas from which we can never upgrade.
Contributes to issue CURA-8466.
It is no longer used since we've removed the Fill Gaps Between Walls setting. This setting is no longer referred to from CuraEngine.
Contributes to issue CURA-8466.
Also removed this mistake from Arachne Beta 1. Cura 4.13 already had stack version 5, so it's no longer necessary to have both.
Contributes to issue CURA-8466.
It's going to upgrade from 4.13 to 5.0. We will not support an upgrade path from the alpha/preview-betas to the stable release.
Contributes to issue CURA-8466.
Conflicts:
resources/definitions/ultimaker2.def.json -> Additions in Arachne around a place where we fixed an enum setting.
resources/definitions/ultimaker3.def.json
resources/definitions/ultimaker_s3.def.json
resources/definitions/ultimaker_s5.def.json
So that they are also mapped from the global qualities to the flsun_sr-specific ones. This way they will be able to still be used in the newer Cura versions.
CURA-8510
Since the setting version 18 is used in the arachne beta build, we decided to make the the setting version to 19 in the normal releases, so that we make sure that projects made in arachne beta won't use any version upgrade scripts if a user attempts to open them in 4.12.
CURA-8510
Currently:
* 48to49 upgrades the machine stacks from 4000016 to 50000**16**
* 49to50 upgrades the machine stacks from 4000016 to 50000**18**
As a result, the versionUpgrader in arachne skips the 48to49 because it sees that the 49to50 also increments the setting version.
This is now fixed by making sure that the 49to50 upgrades from **5**000016 to 5000018.
CURA-8468
We'll offer the option to print from outside to inside, from inside to outside, or from inside to outside except that the very innermost centre wall is printed last.
Contributes to issue CURA-8109.
We want to keep it this way so people can still make plugins work for older versions of Cura, like 3.6, where the 'api' field with just a single major version, instead of the 'supported_sdk_versions', which can be either a version-string like '7.6.0' or a list of version strings.
Conflicts:
cura/CuraApplication.py: Setting version
fdmprinter and fdmextruder: Setting version
intents, qualities and variants: Setting version
Changelog: 4.9.1 was added, should be below Arachne changes
We've seen from experience that people do end up with broken files, due to user-modifications and whatnot. Corrupting it further won't make things better for the user.
Contributes to issue CURA-8212.
If the user account scope is outdated, delete it when upgrading from 4.8 to 4.9. This means that
the user will have to log in again, to make sure they get the correct account scope.
CURA-8093
If the 4.8 is started from a clean install and no category gets expanded in the settings panel,
then the "categories_expanded" key will not exist in the [cura] preferences in cura.cfg.
As a result, when the 4.9 gets started in this specific case, the version upgrade 48 to 49 will
produce a crash and will be considered as "failed", which will then lead to cura requesting from
the user to go from the entire onboarding flow instead of landing on the "What's new" pages (even
though everything else has been properly updated).
This commit fixes that by checking whether the "categories_expanded" key exists in the cura.cfg.
The Cura 4.9 release will have expanded functionality. If you have a plug-in that uses this functionality, marking it as using SDK 7.5.0 will notify older Cura releases that they can't use that plug-in.
