roslaunch in new terminal
Hello, I have a question what should I do if I have situation like this:
I have a launch file "simulation.launch" and in this launch file I have for example launch file for keyboard_teleop_node, but I would like to steer from another terminal so how I should add arguments for this line?
"<include file="$(find my_package)/launch/keyboard_teleop.launch"/>"
What do you mean by "steer from another terminal"?
I mean that I run one launch file and there are some nodes an one launch file is teleoperation node and I want that this launch file starts in other terminal :)
@mopsiu50: please don't post answers, unless you are actually answering a question. For everything else, either edit your question, or use comments.
Why is a feature like "launch-prefix="xterm -e" missing for the <include> tag? I think it's essential. Here is the same question: http://answers.ros.org/question/20314...</include>
Most likely because no one needed it / bothered to implement it. If you feel strongly enough about it and know a bit about Python coding, you could actually add it yourself.
roslaunch
is part of ros_comm. I'd recommend discussion in a ticket before implementing.Strange... At the moment you have to edit the default launch files and add a "launch-prefix" to each nodes you want to start like this.
I don't think it's really so strange: apparently there wasn't a need for this, so it didn't get implemented. Also, consider that launch file
include
s can be recursive, with a nesting depth of 3 launch files (not uncommon), all nodes in all includes launch files would get separate terminals .... for a moderately sized ROS application, that could result in upward of 30 terminals. I'm not sure I would be very happy with that.