'Split' node is still running after behavior has been stopped

[hjhome2000]

Hey,
I found a small bug (but very hard to find) in a Split Node.
Let’s assume Split node has two output flows.
If first flow stops the behavior, the second flow must not be executed.
but its still be executed for current version (v1.3.5). I think its caused by for loop in Split.

Below is the current Split flow execution code:

1 2	for (var i = 0; i < portCount; i++)   outs\[i\].Call(f);

this code should be like this:

1 2 3 4 5

for (var i = 0; i < portCount; i++) {   if (!graph.isRunning)     break;   outs\[i\].Call(f); }

please go over it.
thanks.

[Gavalakis]

Hello,

I think that this is a reasonably correct modification, so I just made this change and will be included in the next version as well 🙂
Thanks.

Join us on Discord: https://discord.gg/97q2Rjh

[Author]

Posts