Publish State Path to ROS Topic when entering a State #161
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Just fyi this pull request won't work. After the merge every custom state has to define the onEnter method. A simple fix is not to remove the definition of onEnter. |
|
This seems reasonable with the fix of leaving onEnter with pass defined. I will plan to make this change on the FlexBE repo (https://github.com/FlexBE/flexbe_behavior_engine/issues) over the next week or so to both ROS 1 develop branch, and the ros2-devel branches on the FlexBE repo. Then close this PR. I do NOT plan to update this older repo. Follow FlexBE/flexbe_behavior_engine#9 for future developments |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Publish the current state path on the topic
flexbe/behavior_updatewhen entering a state.