mirror of
https://github.com/Ultimaker/Cura.git
synced 2025-11-02 20:52:20 -07:00
Add answer commments to some puzzling code
This commit is contained in:
parent
8e891b69b0
commit
e0ad7a9fb4
1 changed files with 3 additions and 0 deletions
|
|
@ -102,6 +102,9 @@ class GlobalStack(CuraContainerStack):
|
||||||
|
|
||||||
# Handle the "resolve" property.
|
# Handle the "resolve" property.
|
||||||
#TODO: Why the hell does this involve threading?
|
#TODO: Why the hell does this involve threading?
|
||||||
|
# Answer: Because if multiple threads start resolving properties that have the same underlying properties that's
|
||||||
|
# related, without taking a note of which thread a resolve paths belongs to, they can bump into each other and
|
||||||
|
# generate unexpected behaviours.
|
||||||
if self._shouldResolve(key, property_name, context):
|
if self._shouldResolve(key, property_name, context):
|
||||||
current_thread = threading.current_thread()
|
current_thread = threading.current_thread()
|
||||||
self._resolving_settings[current_thread.name].add(key)
|
self._resolving_settings[current_thread.name].add(key)
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue