Skip to content
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

Merged
merged 2 commits into from
Mar 7, 2017

Conversation

Jntzko
Copy link
Contributor

@Jntzko Jntzko commented Feb 27, 2017

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.

@Jntzko Jntzko force-pushed the fixMotionPlanningDisplay branch from cf8fc0f to 04c5ca0 Compare February 27, 2017 14:26
Copy link
Contributor

@v4hn v4hn left a 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>
Copy link
Contributor

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?

Copy link
Contributor Author

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.
@Jntzko Jntzko force-pushed the fixMotionPlanningDisplay branch from 04c5ca0 to f16c1ea Compare February 28, 2017 09:45
@v4hn
Copy link
Contributor

v4hn commented Feb 28, 2017

Thank you.
I believe this should be merged and ported to j/k.

@130s 130s merged commit ed43752 into moveit:indigo-devel Mar 7, 2017
@Jntzko Jntzko deleted the fixMotionPlanningDisplay branch March 27, 2017 08:07
JafarAbdi pushed a commit to JafarAbdi/moveit that referenced this pull request Mar 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants