You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SetRemap action was added in #158 to give users an easy way to apply remaps to multiple nodes at the same scope. However, if the SetRemap action is placed inside an include action, then the remappings are not applied.
For example, I want to remap the topic for nodes included in a launch file:
The main reason is that include is defined in launch and not in launch_ros.
That makes sense.
After looking at this again, I was mistakenly thinking that this was possible in ROS 1, but it is not. We accomplish this the same way in ROS 1's roslaunch, e.g.:
Feature request
Feature description
The SetRemap action was added in #158 to give users an easy way to apply remaps to multiple nodes at the same scope. However, if the SetRemap action is placed inside an include action, then the remappings are not applied.
For example, I want to remap the topic for nodes included in a launch file:
But, in order to actually get it to work we have to put the
<set_remap>
action as a peer to<include>
:This is less desirable because the remapping might leak to other nodes at include scope and we're forced to wrap everything in a
<group>
:I don't know if there's a technical reason for the current behavior or if it is simply an oversight.
The text was updated successfully, but these errors were encountered: