Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Solution for #485.
I have taken this approach, searching and stopping all instances of
ros::simple-action-client
registered as slots in the robot-interface instance.https://github.com/Affonso-Gui/roseus_resume/blob/eus10/euslisp/interruption-handler.l#L60-L70
The initialization code is then moved to
robot-interface
, and can be enabled by default in other robots without any modification. Roseus_resume will be automatically disabled on eus9 or when the package is not found, and can also be manually disabled by setting the*enable-roseus-resume*
variable tonil
.Other (user-defined) actions can also be registered as interruption targets by further calling the
roseus_resume:install-interruption-handler
function.If the user doesn't want to interrupt a certain action, this can be achieved by overwriting the
:get-action-status
,:interrupt-angle-vector
, orroseus_resume:on-interruption
.The last one is preferred for local overwrites.