-
Notifications
You must be signed in to change notification settings - Fork 84
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
Add parameter support #112
Conversation
c2362ea
to
5a2b275
Compare
c6db7cc
to
96e67cb
Compare
|
||
auto executor = | ||
rclcpp::executors::MultiThreadedExecutor::make_shared(rclcpp::ExecutorOptions{}, numThreads); | ||
|
||
rclcpp_components::ComponentManager componentManager(executor, "ComponentManager"); | ||
rclcpp_components::ComponentManager componentManager(executor, "foxglove_component_manager"); |
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 may need to be foxglove_bridge_component_manager
if it's supposed to be globally unique in the rosgraph, since we may introduce more Foxglove ROS nodes over time.
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.
Changed during rebasing. Since #125 we could actually get rid of the executable, since one can load the compoment directly in a launch file: https://docs.ros.org/en/humble/How-To-Guides/Launching-composable-nodes.html
d14becf
to
3e84a46
Compare
Public-Facing Changes
Description
Implements support for parameters which was added to the ws-protocol specification in foxglove/ws-protocol#288
This PR is rather big due to the different implementation of parameters for ROS 1 and ROS 2
ROS 1:
ros::NodeHandle::getParamNames
,ros::NodeHandle::getParam
,ros::NodeHandle::setParam
ROS 2 (see also About-ROS-2-Parameters):
list_parameters
,get_parameters
,set_parameters
Fixes #9
FG-1203