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
Currently the implementation of BtActionNode::on_cancelled() returns BT::NodeStatus::SUCCESS. I have found this to be counter-intuitive, as the goal has (by definition) not been successfully completed, and may often require overriding to return a failure.
I would like to get @fmrico's opinion on changing the default behavior to BT::NodeStatus::FAILURE to better reflect what is actually happening.
The text was updated successfully, but these errors were encountered:
Well, the current semantic is BtActionNode::on_cancelled() returns BT::NodeStatus::SUCCESS if the action could be succesfully cancelled. I think it is reasonable, isn't it?
Currently the implementation of
BtActionNode::on_cancelled()
returnsBT::NodeStatus::SUCCESS
. I have found this to be counter-intuitive, as the goal has (by definition) not been successfully completed, and may often require overriding to return a failure.I would like to get @fmrico's opinion on changing the default behavior to
BT::NodeStatus::FAILURE
to better reflect what is actually happening.The text was updated successfully, but these errors were encountered: