From 6522aae915cccb2c2b4c82635dd99377783e326c Mon Sep 17 00:00:00 2001
From: Ghostkeeper <rubend@tutanota.com>
Date: Wed, 25 May 2016 11:50:58 +0200
Subject: [PATCH] Improve slice trigger documentation

Contributes to issue CURA-1278.
---
 plugins/CuraEngineBackend/CuraEngineBackend.py | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/plugins/CuraEngineBackend/CuraEngineBackend.py b/plugins/CuraEngineBackend/CuraEngineBackend.py
index e7fb946bb6..aa42a08393 100644
--- a/plugins/CuraEngineBackend/CuraEngineBackend.py
+++ b/plugins/CuraEngineBackend/CuraEngineBackend.py
@@ -55,10 +55,9 @@ class CuraEngineBackend(Backend):
         self._onActiveViewChanged()
         self._stored_layer_data = []
 
-        #When any setting property changed, call the _onSettingChanged function.
-        #This function will then see if we need to start slicing.
+        #Triggers for when to (re)start slicing:
         if Application.getInstance().getGlobalContainerStack():
-            Application.getInstance().getGlobalContainerStack().propertyChanged.connect(self._onSettingChanged)
+            Application.getInstance().getGlobalContainerStack().propertyChanged.connect(self._onSettingChanged) #Note: Only starts slicing when the value changed.
 
         #When you update a setting and other settings get changed through inheritance, many propertyChanged signals are fired.
         #This timer will group them up, and only slice for the last setting changed signal.