Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal for a rqt_experimental_plugins and rqt_core_plugins packages #167

Closed
ablasdel opened this Issue Aug 26, 2013 · 17 comments

Comments

Projects
None yet
4 participants
@ablasdel
Copy link
Contributor

commented Aug 26, 2013

This package would house new plugins that we would wish to add to common_plugins until they stabilize (have no Major bug Issues etc).

This would give the rqt user a better idea of what plugins we are presenting as stable and fully developed.

It would also help keep the number of issues on the main repo down so it is clear to users what bugs and enhancements we are focusing on.

Less important but it might be wise to have a distinction between the really critical core plugins and the "nice to haves". rqt_core_plugins could house rqt_console, rqt_image_view, rqt_plot and all the other "it is significantly harder to use ROS without a tool like this" plugins.

rqt_common_plugins could house things like rqt_msg, rqt_srv, rqt_action and rqt_web that are useful sometimes but something you could live without.

@DorianScholz

This comment has been minimized.

Copy link
Member

commented Aug 26, 2013

I think it is a good idea to divide the packages.
This helps us focus on the important plugins.
Also this will be visible to users when reporting bugs, as they have to go into the specific packages for that.

But the question is, how are "normal" users of rqt going to see experimental plugins in the GUI?
Should the plugins have the "experimental" in their menu entry, i.e. "plugin name [experimental]"?

@ablasdel

This comment has been minimized.

Copy link
Contributor Author

commented Aug 26, 2013

Good idea on making it also visible in the GUI. A text tag would suffice I think. Though we would have to add a flag for this state in the plugin.xml. I would suggest a "stable=true" flag somewhere to be added only once a plugin has officially left experimental status.

I was thinking we wouldn't install them with "desktop" but making the status visible would be another option.

@dirk-thomas

This comment has been minimized.

Copy link
Member

commented Aug 26, 2013

Splitting the "experimental" plugins into their own repo does not really buy us anything. On the positive side the tickets get separated but on the negative side reintegrating them later with history is more of a challenge. The most significant thing is that the user does not even notice so nothing changes from his impression that the plugin is supposed to work. Anyway splitting each plugin into its own repo could be a good thing in the long run - also to decouple their releases.

We might want to consider to group all the plugins in the plugin menu. On the one hand that would anyway be useful since the plain list gets already pretty long and confusing. On the other hand we could use one group name like "under development" / "experimental" and put some plugins there.

Would someone put together a complete list of plugins and propose a grouping of them?

@ablasdel

This comment has been minimized.

Copy link
Contributor Author

commented Aug 26, 2013

+1 splitting plugins into their own repos and as long as we keep sort of "plugin release groups" concept so they can be easily installed enmass.

+1 adding some sort of groups tag to the pluglin.xml to use for hierarchy in the drop down.

I'll look into some possible groupings for the plugins we currently have.

@dirk-thomas

This comment has been minimized.

Copy link
Member

commented Aug 26, 2013

rqt already supports grouping (even nested).

Just propose a list so we can iterate them - I can then deploy the necessary changes.

@ablasdel

This comment has been minimized.

Copy link
Contributor Author

commented Aug 26, 2013

Here is a preliminary grouping that seems to make sense:

Group names are up for debate obviously

Introspect ROS System:
Action Introspection
Message Introspection
Service Introspection
Package Graph

View/Edit ROS State:
Bag
Console
Dynamic Reconfigure
Graph
Launch
Logger Level
Publisher
ServiceCaller
Top / Process Monitor
Topic Introspection

Visualization:
GPS
Image View
Plot
Navigation Viewer
RViz
TF Tree

Robot Command:
PR2 PBD GUI
Robot Steering
Moveit! monitor

Robot Monitoring:
Kobuki Desktop
PR2 Dashboard
PR2 motor diagnostic
Runtime Monitor
Robot Monitor

Tools:
Shell
PyConsole
Webtool integration

Experimental:
New plugins go here!

@dirk-thomas

This comment has been minimized.

Copy link
Member

commented Aug 26, 2013

  • Introspect ROS System:
    I would call this differently. "Topic introspection" not being in it already indicates that the grouping naming is difficult. It should contain something in the name which makes clear that these plugins deal with static information of ROS only. The list information available without running anything and introspection often refers to look into a running system. Probably call it "Static ROS information"?
  • View/Edit ROS State:
    In contrast to the first group these plugins deal with a running ROS system and allow to view information as well as to manipulate it. I am not very happy with the proposed name but don't have anything better to offer right now. Any other ideas?
  • Some plugin classifications are not obvious to me:
    • What does "Moveit! monitor" do? Can it really "command" or should it be under "Robot monitoring"?
    • What does the "Runtime Monitor" do? Is it the diagnostic part of the dashboards? Why is it under "Robot Monitoring"?
  • Should we have a group for every specific robot? E.g. all PR2 specific plugins go into a "PR2" group.
@ablasdel

This comment has been minimized.

Copy link
Contributor Author

commented Aug 26, 2013

I agree the names need serious work. Any ideas welcome.

For "introspect system". I was thinking more of things at look of the state
of the ROS install

For view edit I was thinking things that look at actively moving ROS parts.
(Which is why topic introspect lived here.

I guessed on move it monitor. If I was wrong it can be moved.

Runtime monitor is a basic diagnostic aggregator viewer. Robot monitor is
similar but give quite a few more features for looking at previous states
and pulling out error/warn states.

I like the idea of robot specific groups and then a " robot monitoring" for
the basic "all robots can use these" things

On Monday, August 26, 2013, Dirk Thomas wrote:

Introspect ROS System:
I would call this differently. "Topic introspection" not being in it
already indicates that the grouping naming is difficult. It should contain
something in the name which makes clear that these plugins deal with static
information of ROS only. The list information available without running
anything and introspection often refers to look into a running system.
Probably call it "Static ROS information"?

View/Edit ROS State:
In contrast to the first group these plugins deal with a running ROS
system and allow to view information as well as to manipulate it. I am not
very happy with the proposed name but don't have anything better to offer
right now. Any other ideas?

Some plugin classifications are not obvious to me:
- What does "Moveit! monitor" do? Can it really "command" or should
it be under "Robot monitoring"?
- What does the "Runtime Monitor" do? Is it the diagnostic part of
the dashboards? Why is it under "Robot Monitoring"?
-

Should we have a group for every specific robot? E.g. all PR2 specific
plugins go into a "PR2" group.


Reply to this email directly or view it on GitHubhttps://github.com//issues/167#issuecomment-23291506
.

@wjwwood

This comment has been minimized.

Copy link
Member

commented Aug 26, 2013

This is how I would organize them with some plugin name changes for consistency. Obviously these are just my opinion, not sure how we can iterate on this:

  • Actions
    • Action Caller # This doesn't exist yet
    • Action Type Browser # formerly Action Type Introspection
  • Services
    • Service Caller # formerly ServiceCaller
    • Service Type Browser # formerly Service Introspection
  • Topics
    • Message Type Browser # formerly Message Introspection
    • Topic Monitor # formerly Topic Introspection
    • Topic Publisher # formerly Publisher
  • Logging
    • Console
    • Logger Level
    • Bag
  • Introspection
    • Package Graph
    • Top / Process Monitor
    • Node Graph
    • Dynamic Reconfigure
    • Launch
  • Visualization
    • GPS
    • Image View
    • Plot
    • Navigation Viewer
    • RViz
    • TF Tree
  • Robot Tools
    • Robot Steering
    • Robot Monitor # Consider renaming to 'Diagnostics Viewer'?
    • Runtime Monitor (Deprecated in favor of Robot Monitor?)
  • PR2
    • PR2 PBD GUI
    • PR2 Dashboard
    • PR2 Motor Diagnostic
  • Kobuki
    • Kobuki Desktop
  • Moveit!
    • Moveit! Monitor
  • Miscellaneous Tools
    • Shell
    • PyConsole
    • Web
  • Experimental
    • New plugins...
@ablasdel

This comment has been minimized.

Copy link
Contributor Author

commented Aug 26, 2013

+1 on William's list/name change iteration.
With some minor issues:
1 Isn't Moveit! a robot tool? it seems pretty general and I would slot it into "robot tools" but you have worked with it more than me.
2 I was told that Runtime Monitor fills a slightly different niche honestly.

@dirk-thomas

This comment has been minimized.

Copy link
Member

commented Aug 27, 2013

Regarding the list from @wjwwood:

  • I would not expect "Launch" to be under "Introspection", I don't see any group where launch really fits in
  • "Robot monitor" aka. "Diagnostics Viewer" sounds a lot like it belongs to "Introspection"
  • "Moveit! Monitor" should not be its own group, it does not really buy us anything

Minor rename:

  • I would rename "Topic Publisher" to "Message Publisher" since that matches ROS terminology better
@dirk-thomas

This comment has been minimized.

Copy link
Member

commented Sep 30, 2013

Slightly refined grouping (as sent to the mailing list):

Actions

  • Action Caller # this doesn't exist yet
  • Action Type Browser # formerly Action Type Introspection

Services

  • Service Caller # formerly ServiceCaller
  • Service Type Browser # formerly Service Introspection

Topics

  • Message Publisher # formerly Publisher
  • Message Type Browser # formerly Message Introspection
  • Topic Monitor # formerly Topic Introspection

Logging

  • Bag
  • Console
  • Logger Level

(How should this group be named?)

  • Dynamic Reconfigure
  • Launch

Introspection

  • Node Graph
  • Package Graph
  • Process Monitor

Visualization

  • GPS
  • Image View
  • Navigation Viewer
  • Plot
  • RViz
  • TF Tree

Robot

  • Kobuki:
    • Kobuki Desktop
  • PR2:
    • PR2 Dashboard
    • PR2 Motor Diagnostic
    • PR2 PBD GUI

Robot Tools

  • Moveit! Monitor
  • Robot Monitor # consider renaming to 'Diagnostics Viewer'?
  • Robot Steering
  • Runtime Monitor

Miscellaneous Tools

  • PyConsole
  • Shell
  • Web
  • New plugins (experimental) # marked as experimental until they are stable

Updated based on feedback:

  • each robot group (Kobuki, PR2 etc.) is now nested under a generic group called Robot
  • marking experimental plugins with (experimental) but keeping them in the group they belong to
@DorianScholz

This comment has been minimized.

Copy link
Member

commented Oct 1, 2013

+1 for the hierarchy
But instead of putting all new/experimental plugins in one group, shouldn't they directly go into the appropriate group and have an "(experimental)" suffix?
This would allow them to be found more easily after they have matured and still tell the user not to expect a stable plugin yet.

@dirk-thomas

This comment has been minimized.

Copy link
Member

commented Oct 1, 2013

@DorianScholz good point - I updated the above list.

@dirk-thomas

This comment has been minimized.

Copy link
Member

commented Nov 27, 2013

@dirk-thomas

This comment has been minimized.

Copy link
Member

commented Nov 27, 2013

I marked rqt_launch and rqt_reconfigure with an "experimental" suffix in the plugin menu. This is mainly due to the number of open ticket for those plugins which describe severe defects in functionality.

@ghost ghost assigned dirk-thomas Nov 27, 2013

@dirk-thomas

This comment has been minimized.

Copy link
Member

commented Nov 27, 2013

Please consider checking out the latest versions of the plugin repo and see for yourself if the grouping makes sense.

I will mark this ticket as closed. If you have further feedback/suggestions please feel free to comment .

severin-lemaignan pushed a commit to severin-lemaignan/robotpkg that referenced this issue Aug 18, 2014

Anthony Mallet
[graphics/ros-rqt-common-plugins] Update to 0.3.8
Changes since 0.2.16:

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Changelog for package rqt_reconfigure
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

0.3.8 (2014-07-15)
------------------

0.3.7 (2014-07-11)
------------------
* fix slider bar, add context menus for common operations (`#251
<https://github.com/ros-visualization/rqt_common_plugins/issues/251>`_)
* fix bug in float range calculations (`#241
<https://github.com/ros-visualization/rqt_common_plugins/issues/241>`_)
* remove experimental suffix from rqt_reconfigure (`#256
<https://github.com/ros-visualization/rqt_common_plugins/issues/256>`_)
* export architecture_independent flag in package.xml (`#254
<https://github.com/ros-visualization/rqt_common_plugins/issues/254>`_)

0.3.6 (2014-06-02)
------------------
* remove unnecessary margins to improve usability on small screens (`#228
<https://github.com/ros-visualization/rqt_common_plugins/issues/228>`_)

0.3.5 (2014-05-07)
------------------
* numerous improvements and bug fixes (`#209
<https://github.com/ros-visualization/rqt_common_plugins/pull/209>`_, `#210
<https://github.com/ros-visualization/rqt_common_plugins/pull/210>`_)
* add option to open list of names from command line (`#214
<https://github.com/ros-visualization/rqt_common_plugins/pull/214>`_)

0.3.4 (2014-01-28)
------------------

0.3.3 (2014-01-08)
------------------
* add groups for rqt plugins, renamed some plugins (`#167
<https://github.com/ros-visualization/rqt_common_plugins/issues/167>`_)
* mark rqt_launch and rqt_reconfigure as experimental (`#167
<https://github.com/ros-visualization/rqt_common_plugins/issues/167>`_)

0.3.2 (2013-10-14)
------------------

0.3.1 (2013-10-09)
------------------

0.3.0 (2013-08-28)
------------------
* fix updating range limits (`#108
<https://github.com/ros-visualization/rqt_common_plugins/issues/108>`_)
* fix layout quirks (`#150
<https://github.com/ros-visualization/rqt_common_plugins/issues/150>`_)
* fix icon for closing a node (`#48
<https://github.com/ros-visualization/rqt_common_plugins/issues/48>`_)
* fix handling of enum parameters with strings

0.2.17 (2013-07-04)
-------------------
* Improvement; "GUI hangs for awhile or completely, when any one of nodes
doesn't return any value" (`#81
<https://github.com/ros-visualization/rqt_common_plugins/issues/81>`_)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Changelog for package rqt_topic
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

0.3.8 (2014-07-15)
------------------

0.3.7 (2014-07-11)
------------------
* export architecture_independent flag in package.xml (`#254
<https://github.com/ros-visualization/rqt_common_plugins/issues/254>`_)

0.3.6 (2014-06-02)
------------------

0.3.5 (2014-05-07)
------------------

0.3.4 (2014-01-28)
------------------

0.3.3 (2014-01-08)
------------------
* add groups for rqt plugins, renamed some plugins (`#167
<https://github.com/ros-visualization/rqt_common_plugins/issues/167>`_)
* catch and show exceptions `#198
<https://github.com/ros-visualization/rqt_common_plugins/issues/198>`_

0.3.2 (2013-10-14)
------------------

0.3.1 (2013-10-09)
------------------
* improve rqt_topic initialization time (`#62
<https://github.com/ros-visualization/rqt_common_plugins/issues/62>`_)
* modified toggling topics to use checkbox instead of context menu (`#75
<https://github.com/ros-visualization/rqt_common_plugins/issues/75>`_)

0.3.0 (2013-08-28)
------------------
* fix cleaning old data in rqt_topic (fix `#74
<https://github.com/ros-visualization/rqt_common_plugins/issues/74>`_)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Changelog for package rqt_top
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

0.3.8 (2014-07-15)
------------------

0.3.7 (2014-07-11)
------------------
* export architecture_independent flag in package.xml (`#254
<https://github.com/ros-visualization/rqt_common_plugins/issues/254>`_)

0.3.6 (2014-06-02)
------------------

0.3.5 (2014-05-07)
------------------

0.3.4 (2014-01-28)
------------------
* fix sort order for numerical fields (`#205
<https://github.com/ros-visualization/rqt_common_plugins/issues/205>`_)

0.3.3 (2014-01-08)
------------------
* add groups for rqt plugins, renamed some plugins (`#167
<https://github.com/ros-visualization/rqt_common_plugins/issues/167>`_)
* fix an error caused by SIGKILLing nodes

0.3.2 (2013-10-14)
------------------

0.3.1 (2013-10-09)
------------------

0.3.0 (2013-08-28)
------------------
* remove copy of psutil module and implement missing function (`#105
<https://github.com/ros-visualization/rqt_common_plugins/issues/105>`_)

0.2.17 (2013-07-06)
-------------------
* Embeds python-psutil in the package in order to be enabled on Ubuntu Precise
* first release of this package into hydro

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Changelog for package rqt_image_view
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

0.3.8 (2014-07-15)
------------------

0.3.7 (2014-07-11)
------------------

0.3.6 (2014-06-02)
------------------

0.3.5 (2014-05-07)
------------------
* list image transport topics if parent image topic is not available (`#215
<https://github.com/ros-visualization/rqt_common_plugins/issues/215>`_)

0.3.4 (2014-01-28)
------------------

0.3.3 (2014-01-08)
------------------
* add groups for rqt plugins, renamed some plugins (`#167
<https://github.com/ros-visualization/rqt_common_plugins/issues/167>`_)
* properly handle aligned images
* wrap cv calls in try-catch-block (`#201
<https://github.com/ros-visualization/rqt_common_plugins/issues/201>`_)

0.3.2 (2013-10-14)
------------------

0.3.1 (2013-10-09)
------------------
* fix event handling for rqt_image_view enabling to run multiple instances
simultaneously (`#66
<https://github.com/ros-visualization/rqt_common_plugins/issues/66>`_)
* add rqt_image_view to global bin (`#168
<https://github.com/ros-visualization/rqt_common_plugins/issues/168>`_)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Changelog for package rqt_bag_plugins
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

0.3.8 (2014-07-15)
------------------
* fix missing installation of resource subfolder

0.3.7 (2014-07-11)
------------------
* add plotting plugin (`#239
<https://github.com/ros-visualization/rqt_common_plugins/issues/239>`_)
* fix rqt_bag to plot array members (`#253
<https://github.com/ros-visualization/rqt_common_plugins/issues/253>`_)
* export architecture_independent flag in package.xml (`#254
<https://github.com/ros-visualization/rqt_common_plugins/issues/254>`_)

0.3.6 (2014-06-02)
------------------

0.3.5 (2014-05-07)
------------------
* fix PIL/Pillow error (`#224
<https://github.com/ros-visualization/rqt_common_plugins/issues/224>`_)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Changelog for package rqt_plot
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

0.3.8 (2014-07-15)
------------------
* fix missing installation of Python subpackage

0.3.7 (2014-07-11)
------------------
* fix missing import (`#248
<https://github.com/ros-visualization/rqt_common_plugins/issues/248>`_)
* significant improvements and unification of different plot backends (`#239
<https://github.com/ros-visualization/rqt_common_plugins/issues/239>`_, `#231
<https://github.com/ros-visualization/rqt_common_plugins/issues/231>`_)
* make more things plottable including arrays and simple message types (`#246
<https://github.com/ros-visualization/rqt_common_plugins/issues/246>`_)
* make DataPlot a proxy for its plot widget, redraw after loading new data, add
clear_values (`#236
<https://github.com/ros-visualization/rqt_common_plugins/issues/236>`_)
* export architecture_independent flag in package.xml (`#254
<https://github.com/ros-visualization/rqt_common_plugins/issues/254>`_)

0.3.6 (2014-06-02)
------------------
* subscribe to any known topic, even if currently not available (`#233
<https://github.com/ros-visualization/rqt_common_plugins/pull/233>`_)

0.3.5 (2014-05-07)
------------------
* change minimum padding to enable viewing arbitrarily small values (`#223
<https://github.com/ros-visualization/rqt_common_plugins/pull/223>`_)
* redraw plot only on new data to reduce cpu load, especially with matplot
(`#219 <https://github.com/ros-visualization/rqt_common_plugins/issues/219>`_)

0.3.4 (2014-01-28)
------------------

0.3.3 (2014-01-08)
------------------
* add groups for rqt plugins, renamed some plugins (`#167
<https://github.com/ros-visualization/rqt_common_plugins/issues/167>`_)
* add checkbox to toggle automatic scrolling of plot with data
* add simple legend for pyqtgraph backend

0.3.2 (2013-10-14)
------------------

0.3.1 (2013-10-09)
------------------

0.3.0 (2013-08-28)
------------------
* fix waiting on unpublished topics (`#110
<https://github.com/ros-visualization/rqt_common_plugins/issues/110>`_)
* fix rendering of icons on OS X (`ros-visualization/rqt#83
<https://github.com/ros-visualization/rqt/issues/83>`_)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Changelog for package rqt_console
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

0.3.8 (2014-07-15)
------------------

0.3.7 (2014-07-11)
------------------
* export architecture_independent flag in package.xml (`#254
<https://github.com/ros-visualization/rqt_common_plugins/issues/254>`_)

0.3.6 (2014-06-02)
------------------

0.3.5 (2014-05-07)
------------------

0.3.4 (2014-01-28)
------------------

0.3.3 (2014-01-08)
------------------
* add groups for rqt plugins, renamed some plugins (`#167
<https://github.com/ros-visualization/rqt_common_plugins/issues/167>`_)
* use icons instead of text when available, refactor pause/resume button

0.3.2 (2013-10-14)
------------------

0.3.1 (2013-10-09)
------------------
* rewrite of rqt_console to drastically improve performance (`#186
<https://github.com/ros-visualization/rqt_common_plugins/pull/186>`_)

0.3.0 (2013-08-28)
------------------
* pause button no more saves state (`#125
<https://github.com/ros-visualization/rqt_common_plugins/issues/125>`_)
* persist message limit (`#138
<https://github.com/ros-visualization/rqt_common_plugins/issues/138>`_)
* add ability to set logger level (`#117
<https://github.com/ros-visualization/rqt_common_plugins/issues/117>`_)
* add tooltips to table cells (`#143
<https://github.com/ros-visualization/rqt_common_plugins/issues/143>`_)
* improve labels for filters (`#146
<https://github.com/ros-visualization/rqt_common_plugins/issues/146>`_)
* fix time column when loading data from file (`#160
<https://github.com/ros-visualization/rqt_common_plugins/issues/160>`_)
* fix applying message limit on change (`#133
<https://github.com/ros-visualization/rqt_common_plugins/issues/133>`_)
* fix clear button to remove all messages (`#141
<https://github.com/ros-visualization/rqt_common_plugins/issues/141>`_)
* fix sorting to use row index to decide order between equal values (except for
time column) (`#124
<https://github.com/ros-visualization/rqt_common_plugins/issues/124>`_)
* fix locking of message queue
* fix rendering of icons on OS X (`ros-visualization/rqt#83
<https://github.com/ros-visualization/rqt/issues/83>`_)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Changelog for package rqt_graph
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

0.3.8 (2014-07-15)
------------------

0.3.7 (2014-07-11)
------------------
* fix compatibility with Groovy, use TopicStatistics only if available (`#252
<https://github.com/ros-visualization/rqt_common_plugins/issues/252>`_)
* export architecture_independent flag in package.xml (`#254
<https://github.com/ros-visualization/rqt_common_plugins/issues/254>`_)

0.3.6 (2014-06-02)
------------------

0.3.5 (2014-05-07)
------------------
* add displaying of topic/connection statistics along edges (`#214
<https://github.com/ros-visualization/rqt_common_plugins/pull/214>`_)
* using CATKIN_ENABLE_TESTING to optionally configure tests (`#220
<https://github.com/ros-visualization/rqt_common_plugins/pull/220>`_)

0.3.4 (2014-01-28)
------------------

0.3.3 (2014-01-08)
------------------
* add groups for rqt plugins, renamed some plugins (`#167
<https://github.com/ros-visualization/rqt_common_plugins/issues/167>`_)

0.3.2 (2013-10-14)
------------------

0.3.1 (2013-10-09)
------------------
* modified zooming method to work better on high-res trackpads like Macbook
Pros (`#187
<https://github.com/ros-visualization/rqt_common_plugins/pull/187>`_)

0.3.0 (2013-08-28)
------------------
* fix rendering of icons on OS X (`ros-visualization/rqt#83
<https://github.com/ros-visualization/rqt/issues/83>`_)

0.2.17 (2013-07-04)
-------------------
* Improve checkbox labels and tooltips wording.

dirk-thomas added a commit to ros-visualization/rqt_moveit that referenced this issue Apr 25, 2017

dirk-thomas added a commit to ros-visualization/rqt_nav_view that referenced this issue Apr 25, 2017

dirk-thomas added a commit to ros-visualization/rqt_robot_monitor that referenced this issue Apr 25, 2017

dirk-thomas added a commit to ros-visualization/rqt_robot_steering that referenced this issue Apr 25, 2017

dirk-thomas added a commit to ros-visualization/rqt_runtime_monitor that referenced this issue Apr 25, 2017

dirk-thomas added a commit to ros-visualization/rqt_rviz that referenced this issue Apr 25, 2017

dirk-thomas added a commit to ros-visualization/rqt_tf_tree that referenced this issue Apr 25, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.