You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During testing I have noticed that the concurrent state only calls the on_start() and on_stop() functions of the state that receives the arrow. In addition, when running a looping behavior like the one described in the image, only the on_enter() and on_exit() functions are called of the state that receives the initial state arrow inside the concurrent state.
I would expect all of the on_enter() and on_exit() functions for each internal state to get called every time the concurrent state is activated.
It works perfect the first time the concurrent state is activated, but then doesn't any other time the state is activated after the first. Killing the behavior and restarting it fixes the problem. I don't have to restart FlexBE for that to happen.
During testing I have noticed that the concurrent state only calls the
on_start()
andon_stop()
functions of the state that receives the arrow. In addition, when running a looping behavior like the one described in the image, only theon_enter()
andon_exit()
functions are called of the state that receives the initial state arrow inside the concurrent state.I would expect all of the
on_enter()
andon_exit()
functions for each internal state to get called every time the concurrent state is activated.It works perfect the first time the concurrent state is activated, but then doesn't any other time the state is activated after the first. Killing the behavior and restarting it fixes the problem. I don't have to restart FlexBE for that to happen.
Concurrent test behavior:
concurrent_test_behaviors.tar.gz
Log output when running the behavior:
concurrent_test.txt
The logger I used to test:
verbose_logger.txt
(It's a .py in disguise. GitHub wouldn't let me upload a .py)
The text was updated successfully, but these errors were encountered: