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.
This commit is contained in:
Ghostkeeper 2016-09-08 11:51:33 +02:00
parent 1e23141b18
commit 03c3b2ac2f
No known key found for this signature in database
GPG key ID: 701948C5954A7385

View file

@ -91,7 +91,7 @@ class MachineInstance:
if has_machine_qualities: #This machine now has machine-quality profiles. if has_machine_qualities: #This machine now has machine-quality profiles.
active_material += "_" + variant_materials #That means that the profile was split into multiple. 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: else:
current_settings = self._name + "_current_settings" current_settings = self._name + "_current_settings"