I was wondering how does the attribute of Dynamic work in detail.
The information of document show that “A Dynamic Sequencer will re-evaluate higher priority children Status changes”.Could you please show us some specified examples?
What’s more, I came across one situation that there were two nodes running at the same time when I selected the Dynamic.Why does it happen?Is it right?
Let me learn if you have further information about Dynamic please.I really appreciate any help you can provide.
About “Dynamic” option of composites, have you read the [Reactive Evaluation] documentation section? It clarifies what the “Dynamic” option does, but if you still have questions about it’s usage, please let me know know.
Regarding, two actions running at the same time, this should not happen, at least not with the setup I see in your screenshot. I tried replicating this, but it works correctly. There used to be a bug a few versions back though. What version of NodeCanvas are you currently using?
Also, judging from the screenshot, it mostly looks that it is a bug in the connection UI somehow, because the action on the left does not have the “clock” icon and neither is highlighted as yellow (which is always more correct than what the connection color show).
Can you please send me a small reproduction project that is showcasing this issue if possible?
I have read the [Reactive Evaluation] documentation section.The example of documentation section is same as my project, but it doesn’t work similarly.In general, taking my project for example, the right action should be interrupted immediately and return failure.After that, the left action will execute, right? However, the right action execute one more time after it was interrupted.It really confuse me a lot.
The version of NodeCanvas is v2.6.3 .I don’t think it is a UI bug because the program runs by following the graph.The screenshot can not show more information about the program.
I couldn’t send you a small project because our project of team have developed for long time.It’s hard to make a demo to send to you.I am so sorry for that.I can provide more test information to you as much as you want.If you confirm that it is a bug of the version, I will upgrade the NodeCanvas to fix it.
There was indeed a fix that was found and applied in latest version 2.6.4 regarding Dynamic Sequencers and Selectors. From the change log: Fix: Dynamic Sequencer and Selector, from not reseting all child nodes on interruption. 🙂
I’d recommend to please upgrade and let me know if you encounter any further problems with this.
Thank you!