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

BUG: Fix warning messages when creating markups with no display nodes #7747

Merged
merged 1 commit into from
May 17, 2024

Conversation

Sunderlandkyl
Copy link
Member

Ex:

vtkMRMLMarkupsDisplayableManagerHelper: Failed to create widget

vtkMRMLMarkupsDisplayableManagerHelper: Failed to create interaction widget

Returns without an error message when trying to create a widget if either the markups node or a display node is missing. The widget will be created once both nodes are present.

Copy link
Contributor

@lassoan lassoan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thank you. These warnings were bothering me, too. I just added two trivial comments inline.

Ex:
> vtkMRMLMarkupsDisplayableManagerHelper: Failed to create widget

> vtkMRMLMarkupsDisplayableManagerHelper: Failed to create interaction widget

Returns without an error message when trying to create a widget if either the markups node or a display node is missing.
The widget will be created once both nodes are present.
@Sunderlandkyl
Copy link
Member Author

Thanks @lassoan, comments added.

Copy link
Contributor

@lassoan lassoan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, it looks good.

@lassoan lassoan merged commit 7f4e1f4 into Slicer:main May 17, 2024
5 checks passed
@Sunderlandkyl Sunderlandkyl deleted the markups_widget_warning_fix branch May 17, 2024 14:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants