-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add include guard to materials #1637
Add include guard to materials #1637
Conversation
Prevents material already defined errors when adding multiple types of camera to a robot
I think your suggestion regarding the materials as macros is very reasonable. |
Can you please bloom the ROS1 version of this package with that fix? The latest compiled .deb version still appears to be 2.3.2, which has the bug that this PR fixes. |
@civerachb-cpr sorry, we are no longer maintaining the ROS1 version, focus is on ROS2 only. |
Ouf, just ran into this bug on a robot I'm working on. This fix would be very welcome in the ROS1 .deb! |
I ran into this issue and found this PR. The PR suggests the following change but this change is not made in the PR itself. Is this expected? I think without this change, we still get the message
|
Prevents material already defined errors when adding multiple types of camera to a robot.
I was making a URDF for the d455 based on the d435 as I have a robot with both on and I ran into a material is not unique error. This fixes that.
I think it would actually be better if the materials were macros like
Then changing the places they get used from
<material name="plastic"/>
to<xacro:plastic_material />
That way you don't end up putting very generic names like "aluminum" and "plastic" in the global namespace.