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

Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Revision history [back]

I'm not sure to understand your problem, but could't you run the roscore in a terminal A, the GUI in a terminal B and your core application in a terminal C? Moreover (I don't know if this can be useful) you could set the property required="true" for the node that launches the GUI, so that when the GUI is killed, all other nodes started from the same launch file should die.

I'm not sure to understand your problem, but could't you run the roscore in a terminal A, the GUI in a terminal B and your core application in a terminal C? Moreover (I don't know if this can be useful) you could set the property required="true" for the node that launches the GUI, so that when the GUI is killed, all other nodes started from the same launch file should die.

EDIT:

To make a launch file wait for a roscore you should put --wait in the command line, as described here

ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.

Powered by Askbot version 0.10.2