Closed LKSeng closed 1 year ago
In fact, if rviz_rotatable_image_plugin::ImageRotated
was opened first, followed by a rviz::Image
, a rotation on rviz_rotatable_image_plugin
also applies the same rotation to rviz::Image
... either way, the no mixing rule applies until further notice.
The issue was due to an object in rviz::Image
and rviz_rotatable_plugin::ImageRotated
identifying themselves with the same name. By giving ImageRotated
a different string, similar to namespacing, this apparent coupling is avoided.
It was observed, experimentally, that the
rviz_rotatable_image_plugin::ImageRotated
sometimes show no image if used withrviz::Image
, amongst other effects such as displaying images from the wrong topic. One may also seeTried to advertise a service that is already advertised in this node [/rviz_1683192315335198017/compressed/set_parameters]
on eachImageRotated
instance being enabledstdout
.Workaround: Replace all
rviz::Image
plugins withrviz_rotatable_image_plugin::ImageRotated
if even oneImageRotated
is needed...This is likely due to that fact that this library extensively uses the original
rviz::Image
plugin.Steps to reproduce No Image:
usb_cam
with a physical web cam.Image
plugin subscribed to theusb_cam
image topicImageRotated
plugin subscribed to theusb_cam
image topicImage
plugin. NowImageRotated
shows "No Image".Image
again.ImageRotated
camera image returns.ImageRotated
.Image
remains unaffected.Corollary; the reverse is also true:
usb_cam
with a physical web cam.ImageRotated
plugin subscribed to theusb_cam
image topicImage
plugin subscribed to theusb_cam
image topicImageRotated
plugin. NowImage
shows "No Image".ImageRotated
again.Image
camera image returns.Image
.ImageRotated
remains unaffected.