Is there a common routine for forcing execution order of nodes within patches?
Routines I’ve found so far:
- Node then Node : Put early code into an
Ifregion which is set to
Trueand pass the inputs to the later function through the
Ifregion (e.g. with an IOBox in the middle). I think this was joreg’s method.
- Node then Node : Use
IsAssignednode to take any output of an earlier node and feed it into the
Applyof a later node
- Loop region then Node : Pass something through the accumulator argument which becomes the input for the Node
These types of approaches presume that out earlier nodes have outputs and that our later nodes have inputs (can be forced with
Apply), and we can somehow make a route between the two. I’m a fan of the graph defining the chronology of events, but we might want to be able to have a language-specific feature particualrly for this purpose (perhaps there already is one?), e.g.:
- Expose a special ‘execution order’ pin (perhaps in the IOBox style input/output combined pin to visualise the flow of execution)
- Some kind of layer assignment with priorities (blerggh)
Also I think the editor can be aware of where there are and aren’t ambiguities about execution order in the patch, so any extra interface could be limited to those cases. Also I presume any feature relating to this would be optional via