Dorian Scholz's profile - activity

This a quite a specific and unique setup you have there ;-) So I can't easily reproduce this, but searching for your error message brought me to the Qt.AA_X11InitThreads flag, that can be set before the QApplication is constructed: http://doc.qt.io/qt-4.8/qt.html

This flag is not being set currently by rqt, so you could try running rqt from source and edit the qt_gui/main.py file at about line 173: https://github.com/ros-visualization/...

Directly before the line constructing the QApplication instance add a new line setting the mentioned attribute:

QApplication.setAttribute(Qt.AA_X11InitThreads, True)
app = QApplication(argv)

If that solves your problem, you can file a pull request with this change, so it gets tested on other setups and can hopefully be added to the code.

This was not implemented when you asked. But Austin has been working on related issues and it might be working as you want it now. If not please file as feature request.

Can you change the title of this question to "how to run a newly created rqt plugin". The Answer of "Wolf" is correct, so you can close this afterwards. I also updated the tutorial to avoid this issue.

From your directory structure containing the init.py file src/rqt_bag_comparison/ your module name would be rqt_bag_comparison, not bag_comparison.

So I would guess your plugin.xml has the wrong setting for type. It should be type="rqt_bag_comparison.bag_comparison.BagComparison", if your plugin's class is named BagComparison inside bag_comparison.py.

Not completely sure if I understand your question. rqt_plugins are using the rqt_gui API to add widgets to the main window. You could replicate this API and call the plugins with your own API instance to make them add widgets to your GUI. But why? Rqt allows for arranging multiple plugin widgets...

For me rqt is working fine in fuerte. I don't have hydro installed, only fuerte and groovy and there are no conflicts. It might be a problem in your ROS setup.

Can you check your PYTHONPATH environment variable to not contain any hydro paths. It should look similar to this when in a fuerte bash:

PYTHONPATH=/opt/ros/fuerte/lib/python2.7/dist-packages:/opt/ros/fuerte/lib/python2.7/dist-packages:

I assume you have read the rqt Python plugin tutorial: http://wiki.ros.org/rqt/Tutorials/Wri...

There a UI file is loaded into self._widget which is then added to the main window. What you want to achieve now is to switch the contents of this widget. This is not anymore rqt specific, but a (Py)Qt question. Also there are multiple solutions to this, I think this one found here is what you want: http://stackoverflow.com/questions/46...

The accepted answer tells you to use QStackedWidget with multiple widgets (each loaded from its own UI file) and switch between them: http://pyqt.sourceforge.net/Docs/PyQt...

In you case that would mean creating a QStackedWidget as self._widget and then adding you UI based widgets to it:

self._widget = QStackedWidget()
uiWidget1 = QWidget()
loadUi(ui_file1, uiWidget1)
self._widget.addWidget(uiWidget1)
uiWidget2 = QWidget()
loadUi(ui_file1, uiWidget2)
self._widget.addWidget(uiWidget2)

And then use the setCurrentIndex or setCurrentWidget methods of QStackedWidget to switch widgets in your callback function:

self._widget.setCurrentIndex(0)
self._widget.setCurrentWidget(uiWidget1)

I just had the same problem and was stunned to see how difficult it was to find a simple example for this basic task. So I added a minimal code example to the roslaunch wiki page:

http://wiki.ros.org/roslaunch/API%20U...

Sorry about the long delay for this answer. I updated the wiki page for this plugin to give a short introduction: http://wiki.ros.org/rqt_pose_view

Basically it just displays the orientation part of a geometry_msgs/Pose message. You have to drag and drop the topic onto it...

a workaround to not build PySide bindings has been posted here: https://github.com/ros-visualization/qt_gui_core/issues/35#issuecomment-28527836

The messages you saw are not errors, but merely debug messages. They show that you are missing packages for two of the three available ploting backends:

• MatPlotLib

• PyQtGraph

If they are available pre-packaged for your distribution you can simply install them. If not, at least for PyQtGraph it should be enough the download the source code and put it into your Python path.

Since these two are missing, the least comfortable backend has to be used: QwtDataPlot. This one does not feature auto-scaling and other nice features, which the other two backends have. So if you want this, I suggest installing PyQtGraph.

rqt_plot does not know anything about trajectories, it just plots numeric data over time (like rxplot, but with a choice of multiple plotting backends). Feel free to add a plugin for trajectory plotting, which can reuse the plotting backends.

This is currently not supported, but could be implemented. First as background info, rqt_shell offers three different backends for the actual command shell:

1) one doing a simple single command shell call for each command given

2) one based on the Spyder project's shell

3) one using an actual XTerm instance and just embedding its window into rqt_gui

For 1) the script would have to be executed every time before the command, since the shell used only lives for the execution time of that single command.

For 2) the script has to be run once after the shell is set up.

For 3) the script would have to be passed as command line parameter when starting the XTerm instance.

Please feel free to supply patches implementing any or preferably all of these.

This was certainly true for PySide 1.0.6, but has anyone checked if it changed in more recent versions?

As mentioned above the segfault is most likely bug #16. If you are not using C++ Plugins (image_viewer and rviz [broken]) a quick workaround is to delete the C++ extension: sudo rm /opt/ros/groovy/lib/python2.7/dist-packages/qt_gui_cpp/libqt_gui_cpp_sip.so

This does not work. But I would consider implementing the use of the environment variable "QT_API" as other project already use it to force the binding (i.e. matplotlib).

Using setattr(sys, 'SELECT_QT_BINDING', 'pyside') works, if it is executed before the first import of python_qt_binding. But if your code is running as a rqt plugin, rqt has already imported python_qt_binding, so your plugin cannot change the binding anymore.

To run rqt_gui (and therefore your plugin) with a specific binding use the command line option '--qt-binding' or '-b':

rosrun rqt_gui rqt_gui --qt-binding=pyside

For more command line options see rosrun rqt_gui rqt_gui -h.

rqt will also choose PySide, if PyQt is not installed on the system.

Hi,

I just installed ROS diamondback from the maverick apt sources on Ubuntu 11.04. I'm using only very few stacks, but they seem to work fine. Is there any place where tips about ROS on 11.04 are collected? The fixes I needed to make are the following:

1) The package ros-diamondback-geometry depends on renamed packages sip4 (now python-sip) and python-sip4-dev (now python-sip-dev). To resolve this I created dummy packages with the old names, depending on the new packages. For this I used the tool 'equivs' with minimal config files:

sip4.conf:

Section: misc
Priority: optional
Standards-Version: 3.6.2

Package: sip4
Depends: python-sip
Description: temporary package to satisfy dependencies of Ubuntu 10.10 packages on 11.04

python-sip4-dev.conf:

Section: misc
Priority: optional
Standards-Version: 3.6.2

Package: python-sip4-dev
Depends: python-sip-dev
Description: temporary package to satisfy dependencies of Ubuntu 10.10 packages on 11.04

Then create and install these packages:

$ sudo apt-get install equivs
$ equivs-build sip4.conf
$ equivs-build python-sip4-dev.conf
$ sudo dpkg -i sip4_1.0_all.deb python-sip4-dev_1.0_all.deb

2) To get rid of some compile time dependency errors I added a local rosdep.yaml in the ROS_HOME (usually ~/.ros):

boost:
  ubuntu:
    '11.04': libboost-all-dev
libtool:
  ubuntu: 
    '11.04': libtool libltdl-dev
python-qt4-dev:
  ubuntu: 
    '11.04': python-qt4-dev
python-sip-dev:
  ubuntu: 
    '11.04': python-sip-dev

Good luck Dorian