How to use actions #42
Description
As you said that it is better to define the roles of Activate, Stop and Idle, I opened this thread.
What I intended:
Activate & stop
In general, your planner module is sub process of total mission.
For example, when you perform experiments, your process is hovering -> planning -> landing.
In this case, if your system requires activate and stop, then the actions will serve that purpose.
Idle
HandleIdle normally can do nothing. I just made it so that you can add your action in the future.
For example, when you lose the target, we have to do something, for example looking around with yaw. This behavior can be added if your create HandleExplorationBehavior. You can just remove it if you don't need it.