From 467f971dac2707e07a9f8d80eddad7a4b0ec1945 Mon Sep 17 00:00:00 2001 From: Jaime van Kessel Date: Thu, 28 Jul 2016 15:26:59 +0200 Subject: [PATCH] When sending per object settings, we now also check if we need to send anything at all Adding a setting and then removing it caused some weird behavior issues CURA-1988 --- plugins/CuraEngineBackend/StartSliceJob.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/plugins/CuraEngineBackend/StartSliceJob.py b/plugins/CuraEngineBackend/StartSliceJob.py index ebc4495365..26cf71ec7e 100644 --- a/plugins/CuraEngineBackend/StartSliceJob.py +++ b/plugins/CuraEngineBackend/StartSliceJob.py @@ -211,7 +211,9 @@ class StartSliceJob(Job): def _handlePerObjectSettings(self, node, message): stack = node.callDecoration("getStack") - if stack: + # Check if the node has a stack attached to it and the stack has any settings in the top container. + if stack and stack.getTop().getAllKeys(): + # Because we want to use inheritance correctly, we send all settings as seen from the per object stack. for key in stack.getAllKeys(): setting = message.addRepeatedMessage("settings") setting.name = key