mirror of
https://github.com/Ultimaker/Cura.git
synced 2025-07-07 23:17:32 -06:00
Connect SettingChanged to new propertyChanged function
The listener doesn't properly listen to the signal's parameters yet though. Contributes to issue CURA-1278.
This commit is contained in:
parent
bace52fccf
commit
e5df225b1e
1 changed files with 4 additions and 0 deletions
|
@ -54,6 +54,10 @@ class CuraEngineBackend(Backend):
|
||||||
self._onActiveViewChanged()
|
self._onActiveViewChanged()
|
||||||
self._stored_layer_data = []
|
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.
|
#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.
|
#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.
|
#TODO: Properly group propertyChanged signals by whether they are triggered by the same user interaction.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue