Ghostkeeper 3dc1dbbbdb Load profile from ContainerRegistry if the stack refers to it ... We encountered a case where the version upgrade changed the quality profile to a new one which was specific to the printer rather than a global profile. As the upgraded stack was being read from the project file, it would go look for the new quality profile in the workspace. That ID wouldn't be present in there, and so it would crash and pretend the project file is plain 3MF. This change makes it fallback to the built-in profiles, for precisely such cases as when a version upgrade changes the stack. Contributes to issue CURA-8212.		2021-06-03 17:13:22 +02:00
..
__init__.py	Remove trailing whitespace from Python files	2020-05-29 14:30:33 +02:00
plugin.json	Increment SDK version to 7.5.0	2021-04-06 13:28:08 +02:00
ThreeMFReader.py	Add cura: namespace before setting keys, and store the rest in um_node.metadata	2021-02-08 17:37:38 +01:00
ThreeMFWorkspaceReader.py	Load profile from ContainerRegistry if the stack refers to it	2021-06-03 17:13:22 +02:00
UpdatableMachinesModel.py	Revert "Revert "Merge branch '4.7' of github.com:Ultimaker/Cura into 4.7""	2020-08-20 16:35:52 +02:00
WorkspaceDialog.py	Revert "Revert "Merge branch '4.7' of github.com:Ultimaker/Cura into 4.7""	2020-08-20 16:35:52 +02:00
WorkspaceDialog.qml	Revert "Merge pull request #9716 from Ultimaker/CURA-8010_new_icons"	2021-05-27 16:06:20 +02:00