-
Notifications
You must be signed in to change notification settings - Fork 957
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
correct "simplify widget handling" #452
Conversation
This reverts commit 24adb47.
cf8fc0f
to
04c5ca0
Compare
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.
Except for a nitpick, this looks good to me.
We discovered the problem only after the previous patch was merged, so now we have to revert it.
The new patch seems to address all the problems mentioned in the previous pull request.
@@ -55,6 +56,7 @@ | |||
#endif | |||
|
|||
#include <moveit_msgs/DisplayTrajectory.h> | |||
#include <QDockWidget> |
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 believe this is not needed, because now you use rviz::PanelDockWidget
instead, right?
Could you please remove it from the request?
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.
You're right, I removed it.
This improves on commit: e677d8cc790d91f427606c23717954015f207ef7 With the previous solution, hiding the docking area when the motion planning panel is part of it disabled the whole display including the motion planning *scene* that is displayed in the main window. So instead of relying on the setAssociatedWidget mechanism, we have to implement the wanted behavior ourselves.
04c5ca0
to
f16c1ea
Compare
Thank you. |
The changes from the pull request #442 leads to an error.
Hiding the docking area when the motion planning panel is part of it disabled the whole display including the motion planning scene that is displayed in the main window.
So instead of relying on the setAssociatedWidget mechanism, we have to implement the wanted behavior ourselves.