-
Notifications
You must be signed in to change notification settings - Fork 205
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
Migrate RobotModelDisplay #210
Migrate RobotModelDisplay #210
Conversation
It's possible that some of those files belong in the public part of
If you can try to figure out what was using these functions (interactive markers? something else?) then we could decided if they should be moved to |
LGTM, the only thing I found I was missing was a file browser button in the text box (usually as an ellipsis at the end of the dialog) which would let me browse to a file rather than type it in. For a file, does it need to be a URL? Like |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
code review lgtm too, with one comment for a change or a TODO
rviz_default_plugins/package.xml
Outdated
@@ -35,6 +35,7 @@ | |||
<test_depend>ament_cmake_gmock</test_depend> | |||
<test_depend>ament_cmake_lint_cmake</test_depend> | |||
<test_depend>ament_cmake_uncrustify</test_depend> | |||
<test_depend>dummy_robot_bringup</test_depend> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm hesitant about this, since I don't expect dummy_robot_bringup
to exist forever. I'd rather have it self contained in the rviz repository, though I understand that makes it a lot harder.
I'll take it as-is, but please add a TODO to use something less volatile in the future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree - that's why we added our own urdf file for testing. This is a leftover and we'll remove it. Thanks for catching it!
I'd like to have an answer on the removing dead code question and the dependency on |
Regarding the robot, maybe we really want to explicitly have it in The functionality is never used in RViz (I'll show below). If subclassing is not used outside RViz (probably that can't be answered), the following functions can be removed (links are always to the ROS master and not to our ROS 2 fork):
Suggestion: We'll leave it in |
I added a file picker to the file property. Right now, it'll only work with the normal filepath, no I agree that it might be nice to be able to react to |
- Extract AssimpLoader to new class - Delete code using tinyxml2, use assimp to get the functionality - Scaling is done in the assimp root node
218b9e5
to
c8bc311
Compare
Sounds good to me.
That's fine.
I wasn't thinking that the file picker would be used but result in a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Closes #101
Note that we moved the robot to
rviz_default_plugins
. This means that it is no longer part of any public interface. Is this the way to go?In that case, there is quite some functionality in robot which is part of its public interface but not used in the display. Shall we delete it?