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
The dynamic TF broadcaster object can be initialized.
Actual behavior
It will give you an error.
"passed non-default qos overriding options without providing a parameters interface"
Additional information
I have posted an issue on there and there. I also asked my question there. A friend from ROS2 channel suggested I post my questions there. Please, I really would like to know how to work with tf2_ros::TransformBroadcaster, get_node_xxx_interface, other handles, or something else. I don't want to use 'this' directly. By using node_xxx_handle, I can isolate different functions in different classes without passing the shared printer node everywhere.
The text was updated successfully, but these errors were encountered:
I got an answer from ros2/ros2#1407.
But, can I find some detailed explanation that why we should write the code like this?
Why the code works in old Foxy but will never work in Humble?
What is the mechanism behind these parameters?
There should be a professional channel that we finally find.
Bug report
Ubuntu 22.04.2 LTS
binaries
ROS humble
Fast-RTPS
rclcpp, tf2_ros, tf2, or geometry2
Steps to reproduce issue
Make a dynamic publisher as we always do in foxy.
Expected behavior
The dynamic TF broadcaster object can be initialized.
Actual behavior
It will give you an error.
"passed non-default qos overriding options without providing a parameters interface"
Additional information
I have posted an issue on there and there. I also asked my question there. A friend from ROS2 channel suggested I post my questions there. Please, I really would like to know how to work with tf2_ros::TransformBroadcaster, get_node_xxx_interface, other handles, or something else. I don't want to use 'this' directly. By using node_xxx_handle, I can isolate different functions in different classes without passing the shared printer node everywhere.
The text was updated successfully, but these errors were encountered: