Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/Ultimaker/Cura.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/plugins/VersionUpgrade/VersionUpgrade25to26
AgeCommit message (Collapse)Author
2020-10-22Up the SDK version to 7.4.0Kostas Karmas
In preparation for release of the 4.8. CURA-7795
2020-08-07Update the SDK version to 7.3.0 for 4.7Kostas Karmas
CURA-7641
2020-04-28Remove unneeded unit testsJaime van Kessel
The code was moved to uranium, so no need to test them in a plugin. In some cases they were also testing a specific implementation artifact and not actual expected behavior. CURA-7388
2020-04-22Move the getCfgVersion to base version upgradeJaime van Kessel
They can still be overridden, but in the current situation they were all the same...
2020-04-21Update missed sdk versions from 7.1 to 7.2.0 for Cura 4.6Nino van Hooff
CURA-7383
2020-02-10Bump SDK version number of Cura 4.5 to 7.1Ghostkeeper
We've added new things to our API. This allows plug-in developers to use them. Contributes to issue CURA-7205.
2019-10-21Change SDK version to 7.0.0Nino van Hooff
CURA-6858
2019-08-30Add convenience script for running complete coverageJaime van Kessel
2018-12-17Update plugin versions to match package versionsLipu Fei
CURA-6019
2018-12-14Increment API version to 6Ghostkeeper
All plug-ins now have to re-check whether they are still compatible with the current version of Cura. Contributes to issue CURA-6019.
2018-11-14Fix type of fallback variableGhostkeeper
These have to be strings because the configparser getter can only return strings. Contributes to issue CURA-5936.
2018-11-14Add typing for all version upgrade plug-insGhostkeeper
Hopefully we'll take this typing along when we next copy-paste the stuffs. Contributes to issue CURA-5936.
2018-10-10Code style: Space around binary operatorsGhostkeeper
I just looked for lines with interpolation = None because I was looking for another possible bug, but fixing this in the meanwhile too.
2018-10-03Remove unnecessary import and declaration of i18n in pluginsfieldOfView
2018-09-14Don't depend on the name of resource folders not changingGhostkeeper
If we choose to rename the resource folders, then this plug-in should still look in the old resource folders. So hard-code these resource folders in the state that they were in at version 2.5 so that we can freely change them in a modern version.
2018-08-27Increase plugin API version to 5Aleksei S
CURA-5627
2018-06-11Set encoding correctly when opening files everywhereGhostkeeper
Otherwise the encoding is interpreted differently on Windows and Mac.
2018-03-29CURA-5175 Remove version upgrade of the quality instance containersDiego Prado Gesto
since they never get updated.
2017-10-09Fix container indices in upgrade script from 2.5 to 2.6Lipu Fei
2017-09-28Changing AGPLv3 to LGPLv3Mark
2017-08-22Create user containers for newly created custom FDM printer extrudersLipu Fei
CURA-4188 The newly created extruder stacks don't have user containers, so the user changes cannot be saved. This fix makes sure that in the upgrade, user containers will be created.
2017-08-22Stop the loop if any extruder is foundLipu Fei
CURA-4188
2017-08-22Rename function to _acquireNextUniqueCustomFdmPrinterExtruderStackIdIndex()Lipu Fei
CURA-4188
2017-08-22Add comments for upgradeMachineStack()Lipu Fei
CURA-4188
2017-08-18Fix upgrading custom FDM printers from 2.5Lipu Fei
CURA-4188 Custom FDM printers in 2.5 don't have multi-extrusion support but they do since 2.6. Upgrading from 2.5 to 2.6 will not create the missing extruder stacks for the old custom FDM printers, which causes a crash. This fix makes sure that all custom FDM printers will have 8 extruder stacks during the upgrade so that Cura can still start normally and those printers will still be usable.
2017-07-06Fix upgrade from 2.5 to 2.6 to 2.7Lipu Fei
CURA-3975 - Set Preferences setting_version in CuraApplication so Preferences can get upgraded correctly - Fix upgrade script for 2.5 to 2.6 - Fix upgrade script for 2.6 to 2.7 which relies on the upgrade of 2.5 to 2.6
2017-07-06Remove unused importsLipu Fei
CURA-3975
2017-07-06Fix version upgrade for 2.5 to 2.6Lipu Fei
CURA-3975 - Preferences version is not set correctly - The upgrade script should use a standalone version string because the CuraApplication.SettingVersion can change
2017-06-28Set author to Ultimaker B.V. instead of UltimakerGhostkeeper
To be consistent with the rest of the plug-ins and with the material files. Contributes to issue CURA-3857.
2017-06-22Use semantic versioning for all plugin.jsonLipu Fei
CURA-3712
2017-06-22Fix code styleLipu Fei
CURA-3712
2017-06-21Replaced catalog metadata entry with i18n-catalogJaime van Kessel
CURA-3712 & Cura-3856
2017-06-21Moved certain meta data entries to seperate fileJaime van Kessel
CURA-3856 & CURA-3712
2017-05-19Definition changes are now also upgradedJaime van Kessel
CURA-3837
2017-05-16Fix version upgrade for project loadingLipu Fei
CURA-3756
2017-05-12Add more unhappy-path testsGhostkeeper
One for the new setting_version. One for the misconception of version numbers being a major-minor version or something, because it's not stored that way. Contributes to issue CURA-3427.
2017-05-12Update setting_version testsGhostkeeper
Included a bit of a more difficult case. Contributes to issue CURA-3427.
2017-05-12Load setting version from metadataGhostkeeper
I'm not really awake today, am I? The functionality happened to still work because of how our real data is structured right now, but the tests still failed. Those are successful now. Contributes to issue CURA-3427.
2017-05-12Actually use setting_version to get the setting version numberGhostkeeper
This was sort of hidden because we've always incremented the normal version number up until now. Contributes to issue CURA-3427.
2017-05-12Update tests to account for new way of getting version numbersGhostkeeper
The normal version number is multiplied by a million. Currently these tests fail, so nice to have them. Contributes to issue CURA-3427.
2017-05-12Also update import to renamed packageGhostkeeper
Oops. Contributes to issue CURA-3427.
2017-05-11Track cfg version numbers with major-minor, sortaGhostkeeper
We now have a (format) version and a setting version. Ideally we'd like major-minor version numbers in our profiles. However, introducing major-minor version numbers requires substantial changes to the version upgrade manager to compare version numbers, find a path towards the current version, or even keeping track of the current version. Therefore we just collapse the two version numbers into one: Multiply the major version number by a million and you'll never exceed it in the minor versioning. The only problem is that we now have to update the versioning for all of our three upgrade plug-ins, because they all need to know locally how to find the version number of their file types (because the upgrade manager has no knowledge of the file types) and they have no access to each other because a plug-in may be disabled. Contributes to issue CURA-3427.
2017-05-11Set setting_version in 2.6's profilesGhostkeeper
Contributes to issue CURA-3427.
2017-05-11Remove Cubic Subdivision Radius from users' configurationGhostkeeper
The setting no longer exists. This removes it from all instance containers and preference files. Contributes to issue CURA-3427.
2017-05-11Fix importGhostkeeper
Oops. The test passes again now. Contributes to issue CURA-3427.
2017-05-11Also rename testGhostkeeper
Forgot that, sorry. Contributes to issue CURA-3427.
2017-05-11Rename 24to25 to 25to26Ghostkeeper
The upgrade now upgrades profiles from the 2.5 format to 2.6, since we delayed the update for the 2.5 release. Contributes to issue CURA-3427.
    generated by cgit v1.2.3 (git 2.25.1) at 2024-08-17 00:41:21 +0300