From 69cd00d1c730784e3e1c03db73e2b093b865a4f1 Mon Sep 17 00:00:00 2001 From: Lipu Fei Date: Mon, 30 Oct 2017 13:13:54 +0100 Subject: [PATCH] Do not take into account the active materials when importing a quality profile CURA-4451 When importing a quality profile, it should not fail/succeed based on which materials are activated at the moment. The imported quality profile will be available when the user switches to a compatible settings. --- cura/Settings/CuraContainerRegistry.py | 3 +++ 1 file changed, 3 insertions(+) diff --git a/cura/Settings/CuraContainerRegistry.py b/cura/Settings/CuraContainerRegistry.py index 12f27e8156..e623bd860b 100644 --- a/cura/Settings/CuraContainerRegistry.py +++ b/cura/Settings/CuraContainerRegistry.py @@ -303,6 +303,9 @@ class CuraContainerRegistry(ContainerRegistry): if "material" in quality_type_criteria: materials = ContainerRegistry.getInstance().findInstanceContainers(id = quality_type_criteria["material"]) del quality_type_criteria["material"] + # Do not filter quality containers here with materials because we are trying to import a profile, so it should + # NOT be restricted by the active materials on the current machine. + materials = None # Check to make sure the imported profile actually makes sense in context of the current configuration. # This prevents issues where importing a "draft" profile for a machine without "draft" qualities would report as