Revision history [back]

To compensate for @felix k's answer, rqt saves so-called perspective when it's run on rqt_gui and closed. (I just found that it's not documented) things that are saved include:

• plugins opened
• plugins' size and positions within the container window (rqt_gui)
• rqt_gui's size and position with respect to the computer's desktop

To run rqt_gui, you just run:

$ rqt  (Groovy and later)
$ rqt  (Fuerte)

Running rqt_gui is the recommended usage of rqt, although you can run each rqt plugin individually.

In response to the RViz example in your question, rqt_gui does NOT save the configuration of each plugins as I listed above; instead it's up to how each plugin is implemented. And the feature of rqt variant of Rviz, rqt_rviz, is the same with what RViz has, because rqt_rviz embeds RViz, which doesn't save the .config file that was used the last time as far as I remember. You can open an enhancement request here.

To compensate for @felix k's answer, rqt saves so-called perspective when it's run on rqt_gui and closed. (I just found that it's not documented) things that are saved include:

• plugins opened
• plugins' size and positions within the container window (rqt_gui)
• rqt_gui's size and position with respect to the computer's desktop

To run rqt_gui, you just run:

$ rqt  (Groovy and later)
$ rqt  (Fuerte)

Running rqt_gui is the recommended usage of rqt, although you can run each rqt plugin individually.

In response to the RViz example in your question, rqt_gui does NOT save the configuration of each plugins as I listed above; instead it's up to how each plugin is implemented. And the feature of rqt variant of Rviz, rqt_rviz, is the same with what RViz has, because rqt_rviz embeds RViz, which doesn't save the .config file that was used the last time as far as (if I remember. remember correctly). You can open an enhancement request here.

To compensate for @felix k's answer, rqt saves so-called perspective when it's run on rqt_gui and closed. (I just found that it's not documented) things that are saved include:

• plugins opened
• plugins' size and positions within the container window (rqt_gui)
• rqt_gui's size and position with respect to the computer's desktop

To run rqt_gui, you just run:

$ rqt  (Groovy and later)
$ rqt rosrun rqt_gui rqt_gui  (Fuerte)

Running rqt_gui is the recommended usage of rqt, although you can run each rqt plugin individually.

In response to the RViz example in your question, rqt_gui does NOT save the configuration of each plugins as I listed above; instead it's up to how each plugin is implemented. And the feature of rqt variant of Rviz, rqt_rviz, is the same with what RViz has, because rqt_rviz embeds RViz, which doesn't save the .config file that was used the last time (if I remember correctly). You can open an enhancement request here.