You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #373, the missing behaviour for for-loops to reload the value-links between their input and their children is added. Right now it's by straight-up code duplication from the Macro implementation. Instead this should come from a shared ancestor, e.g. StaticComposite in analogy to StaticNode. Right now that results in a circular import because Composite holds an instance of Creator; in the long run, Workflow should be better extracted from the node hierarchy, it should be the only one to hold the Creator, and I'll be able to introduce such a shared ancestor for these too.
The text was updated successfully, but these errors were encountered:
In #373, the missing behaviour for for-loops to reload the value-links between their input and their children is added. Right now it's by straight-up code duplication from the
Macro
implementation. Instead this should come from a shared ancestor, e.g.StaticComposite
in analogy toStaticNode
. Right now that results in a circular import becauseComposite
holds an instance ofCreator
; in the long run,Workflow
should be better extracted from the node hierarchy, it should be the only one to hold theCreator
, and I'll be able to introduce such a shared ancestor for these too.The text was updated successfully, but these errors were encountered: