From e5df225b1e0e697640208b5d36d5099e8ffad33f Mon Sep 17 00:00:00 2001
From: Ghostkeeper <rubend@tutanota.com>
Date: Mon, 23 May 2016 13:04:36 +0200
Subject: [PATCH] Connect SettingChanged to new propertyChanged function

The listener doesn't properly listen to the signal's parameters yet though.

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

diff --git a/plugins/CuraEngineBackend/CuraEngineBackend.py b/plugins/CuraEngineBackend/CuraEngineBackend.py
index 0c569ce6f3..7aaba3edce 100644
--- a/plugins/CuraEngineBackend/CuraEngineBackend.py
+++ b/plugins/CuraEngineBackend/CuraEngineBackend.py
@@ -54,6 +54,10 @@ 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.
+        Application.getInstance().getGlobalContainerStack().propertyChanged.connect(self._onSettingChanged)
+
         #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.
         #TODO: Properly group propertyChanged signals by whether they are triggered by the same user interaction.