From 03c3b2ac2f62672d5721ed8c51cec7b3eb878a6a Mon Sep 17 00:00:00 2001 From: Ghostkeeper Date: Thu, 8 Sep 2016 11:51:33 +0200 Subject: [PATCH] Make empty profile for current settings when upgrading from UM2+ This change causes the stack to make a new profile at the top to store current settings in. Contributes to issue CURA-844. --- plugins/VersionUpgrade/VersionUpgrade21to22/MachineInstance.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/VersionUpgrade/VersionUpgrade21to22/MachineInstance.py b/plugins/VersionUpgrade/VersionUpgrade21to22/MachineInstance.py index 2147ea9d4f..cab1c00852 100644 --- a/plugins/VersionUpgrade/VersionUpgrade21to22/MachineInstance.py +++ b/plugins/VersionUpgrade/VersionUpgrade21to22/MachineInstance.py @@ -91,7 +91,7 @@ class MachineInstance: if has_machine_qualities: #This machine now has machine-quality profiles. active_material += "_" + variant_materials #That means that the profile was split into multiple. - current_settings = "empty" #The profile didn't know the definition ID when it was upgraded, so it will have been invalid. Sorry, your current settings are lost now. + current_settings = "" #The profile didn't know the definition ID when it was upgraded, so it will have been invalid. Sorry, your current settings are lost now. else: current_settings = self._name + "_current_settings"