mirror of
https://github.com/Ultimaker/Cura.git
synced 2025-07-07 23:17:32 -06:00
Improve slice trigger documentation
Contributes to issue CURA-1278.
This commit is contained in:
parent
9bb4917ae7
commit
6522aae915
1 changed files with 2 additions and 3 deletions
|
@ -55,10 +55,9 @@ class CuraEngineBackend(Backend):
|
||||||
self._onActiveViewChanged()
|
self._onActiveViewChanged()
|
||||||
self._stored_layer_data = []
|
self._stored_layer_data = []
|
||||||
|
|
||||||
#When any setting property changed, call the _onSettingChanged function.
|
#Triggers for when to (re)start slicing:
|
||||||
#This function will then see if we need to start slicing.
|
|
||||||
if Application.getInstance().getGlobalContainerStack():
|
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.
|
#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.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue