Only one custom input is triggered and Subgraphs can (maybe) trigger custom inputs if not active
Mephiztopheles opened this issue · comments
we wanted to create subgraphs to encapsulate actions.
Now we have different timings, when inside the subgraph something should be triggered.
This approach does not seem to work because the custom inputs won't get triggered all. Is that intended?
Is there a better way to achieve our goal?
@Mephiztopheles investigated it :)
Thanks for a nice use case there!
There was an old limitation in code allowing to execute only the first found Custom Input with the given Event Name. Removed that limitation now, so executing events should work now with randomly activated SubGraphs.
Also noticed (and fixed) debugger issue with Custom Input connections - wire coming from this node output wasn't highlighted after activating it.
Small note. In your minimal project, you also got an asset error: Activity subgraph got CustomInput node with the wrong event name. Works fine after selecting a proper name.
