PiotrOrzechowski's profile - activity

Thanks to Daniels accepted answer, I figured out a way to disable log output on ros jade (without compiling ros by yourself).

The rosconsole.cmake did not help, but setting the compile flag in my (package or workspace) CMakeLists.txt is actually working:

set(CMAKE_CXX_FLAGS_RELEASE "${CMAKE_CXX_FLAGS_RELEASE} -DROSCONSOLE_MIN_SEVERITY=5")

As he also points out, the severity level is set in rosconsole.h:

#define ROSCONSOLE_SEVERITY_DEBUG 0
#define ROSCONSOLE_SEVERITY_INFO 1
#define ROSCONSOLE_SEVERITY_WARN 2
#define ROSCONSOLE_SEVERITY_ERROR 3
#define ROSCONSOLE_SEVERITY_FATAL 4
#define ROSCONSOLE_SEVERITY_NONE 5

No more log console prints and file output on Release platforms :)

You have a typo in both plugin.xml and package.xml. It's rqt_gui not qt_gui

Use rqt_gui_py::Plugin as the base class in your plugin.xml file and use

<export>
  <rqt_gui plugin="${prefix}/plugin.xml"/>
</export>

in the manifest.xml

EDIT: Just realized you use rosbuild. But it's still rqt_gui Have a look at this answer: answers.ros.org/question/65679/install-rqt-plugin-with-rosbuild/?answer=65698#post-id-65698 and the rqt_console code for fuerte: github.com/ros-visualization/rqt/tree/fuerte-devel/rqt_console

(Sorry for the unformatted links - my karma is insufficient...)

I experience this bug regularly (adding a nav_msgs/Path topic though)... Luckily we'll switch to hydro, so I hope it works then.

You're right! Unfortunately the ROSNodeTutorialC++ (http://wiki.ros.org/ROSNodeTutorialC%2B%2B) is misleading: It reads the parameters "a", "b" and "message" explicitly from the parameter server even though they are included in the dynamic reconfigure callback...