republish.cpp on humble doesn't support qos overriding on input and output topics when used in cli.
ros2 run image_transport republish compressed raw \
--ros-args -r in/compressed:=/camera1/image_compressed \
-r out:=/camera1/uncompressed
|
auto pub = image_transport::create_publisher(node.get(), out_topic); |
|
auto sub = image_transport::create_subscription( |
|
node.get(), in_topic, |
|
std::bind(pub_mem_fn, &pub, std::placeholders::_1), in_transport); |
The rolling branch has a completely different implementation of republish.cpp - i was curious if it would be possible to backport?
if a backport would break image_common - would it be okay to make a configurable rmw_qos_profile_t struct for configuration when vargv.size() < 3 and set image_transport::create_subscription() and image_transport::create_publisher(). Would this be reasonable?
republish.cppon humble doesn't support qos overriding on input and output topics when used in cli.image_common/image_transport/src/republish.cpp
Line 64 in 5e4dd9e
image_common/image_transport/src/republish.cpp
Lines 71 to 73 in 5e4dd9e
The rolling branch has a completely different implementation of
republish.cpp- i was curious if it would be possible to backport?if a backport would break image_common - would it be okay to make a configurable rmw_qos_profile_t struct for configuration when
vargv.size() < 3and setimage_transport::create_subscription()andimage_transport::create_publisher(). Would this be reasonable?