ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

AFAIK there isn't a way to achieve what you want. The only way I can think of is to create a custom rqt plugin on your own. This custom plugin, however, can be relatively low-cost.

Instead of explaining it in the answer thread, I just added a tutorial section for how to re-use exising (r)qt components.

In your particular scenario, I would do the following, in addition to general steps in the tutorial above:

  • In .ui, define the customwidget as many as you need using the right class from rqt_image_view. Differentiate each instance by name attribute (as instructed in the tutorial).
  • In the program, specify which image topics should go to which image_view instance.

Hope the this makes sense, along with the tutorial just added.

AFAIK there isn't a way to achieve what you want. The only way I can think of is to create want other than creating a custom rqt plugin on your own. This custom plugin, however, can be relatively low-cost.

Instead of explaining it in the answer thread, I just added a tutorial section for how to re-use exising (r)qt components.

In your particular scenario, I would do the following, in addition to general steps in the tutorial above:

  • In .ui, define the customwidget as many as you need using the right class from rqt_image_view. Differentiate each instance by name attribute (as instructed in the tutorial).
  • In the program, specify which image topics should go to which image_view instance.

Hope the this makes sense, along with the tutorial just added.

AFAIK there isn't a way to achieve what you want other than creating a custom rqt plugin on your own. This custom plugin, however, can be relatively low-cost.

Instead of explaining it in the answer thread, I just added a tutorial section for how to re-use exising (r)qt components.

In your particular scenario, I would do the following, in addition to general steps in the tutorial above:

  • In .ui, define the customwidget as many as you need using the right class from rqt_image_view. Differentiate each instance by name attribute (as instructed in the tutorial).
  • In the program, specify which image topics should go to which image_view instance.

Hope the this makes sense, along with the tutorial just added.


Update) @wolf opened another thread http://answers.ros.org/question/201064/custom-rqt-gui/ where a simpler workaround is referenced.