![]() When nodes are added in multiple zones at once, the nodeTree next function does not return a correct list of nodes but repeats some This commit resets the index before starting to call next() to prevent this issue Special thanks to igraecao for the help in finding the bug Co-authored-by: igraecao <matvej.yolli@outlook.com> |
||
---|---|---|
.. | ||
cache | ||
heap | ||
parallelize | ||
queue |