-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Populate Transitions in Transition Events #1140
base: rolling
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -79,6 +79,7 @@ rcl_ret_t | |
RCL_WARN_UNUSED | ||
rcl_lifecycle_com_interface_publish_notification( | ||
rcl_lifecycle_com_interface_t * com_interface, | ||
const char * transition_label, uint8_t transition_id, | ||
const rcl_lifecycle_state_t * start, const rcl_lifecycle_state_t * goal); | ||
Comment on lines
+82
to
83
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. just a curiosity, does that make more sense if that takes There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It would, but originally I just wanted more transparency with what I was adding, that'll be fixed. |
||
|
||
#ifdef __cplusplus | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The clock works, but will the result of
rcutils_system_time_now
serve as the correct time? The transition timestamp is meant to beWhich needs to be set during the period of notification. I can't image trying to pass down a
clock
through multiple layers of API so that the user could set the time that way though.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this will publish the system time only, but i think
LifecycleNode.clock_interface
should be used. more like,rck_lifecycle_com_interface
should be initialized with the same clock with lifecycle node. so that if the node is configured with simulation time, we can also publish the simulation time in the message.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I definitely agree that this would be the best route to go, but will it be problematic making API changes? As the
rcl_lifecycle_com_interface
is changed that means all functions initializingcom_interface
must be changed to include arcl_clock_t *
argument. This would include adding an argument torcl_lifecycle_state_machine_init
and all the functions it calls down the line.