Closed knorth55 closed 7 months ago
Thanks @knorth55 for the contribution, but these kind of things are much better handled with remappings Using params to configure topic names is considered an anti-pattern and so strongly discouraged Moreover, changing RViz config is way easier, as it's all handled internally by RViz, and so much harder to make mistakes
i strongly think it is not a good idea to configure rviz again, because we want to have two different rviz configure for move_base and move_base_flex. at least, i dont want to change plenty of rviz configs we already use.
remapping for simple action server is troublesome so i use rosparam, but it is an anti pattern. you are right.
remapping for simple action server is troublesome so i use rosparam, but it is an anti pattern. you are right.
not 100% sure, but I think it's possible to remap actions :thinking:
yes im sure i can.
but remapping goal, feedback, status, cancel result
is kind of troublesome to me.
anyway this PR is trivial, so it is ok not to be merged.
yes im sure i can. but remapping
goal, feedback, status, cancel result
is kind of troublesome to me. anyway this PR is trivial, so it is ok not to be merged.
no no,,, I mean, remap the action name, not the individual topics (ie move_base --> navigate)
Oh really, can I do that? In that case, I don't need this PR.
this PR accept to change the node name for
legacy relay
. this PR is useful when you want to keep the node name asmove_base
, because somerviz
assumes themove_base
node name. I use as below and I don't need to change rviz config which I used forros-planning/navigation
.move_base_flex_node_name
:move_base
move_base_node_name
:move_base