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

Jump to bottom

qMRMLSegmentationEditorWidget: Unecessary error messages #4664

Closed
slicerbot opened this issue Mar 13, 2020 · 0 comments · Fixed by #4788
Closed

qMRMLSegmentationEditorWidget: Unecessary error messages #4664

slicerbot opened this issue Mar 13, 2020 · 0 comments · Fixed by #4788
Assignees
@Sunderlandkyl
Labels
Priority: Low Small, non-essential improvements or fixes Type: Bug Something isn't working correctly
Milestone
Slicer 4.13

Comments

@slicerbot
Copy link
Collaborator

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
@lassoan lassoan added Priority: Low Small, non-essential improvements or fixes Type: Enhancement Improvement to functionality Type: Bug Something isn't working correctly and removed Type: Enhancement Improvement to functionality labels Mar 21, 2020
@lassoan lassoan added this to the Slicer 4.11.0 milestone Mar 21, 2020
Sunderlandkyl added a commit to Sunderlandkyl/Slicer that referenced this issue Mar 30, 2020
@Sunderlandkyl
BUG: Prevent segment editor error messages on scene close
2792ffe 
- Modified events are now blocked during parameter node initialization
- Error message is not displayed if no parameter node is found during updateWidgetFromMRML
- More thorough error checking for parameter and segmentation nodes in autocomplete effect

fixes Slicer#4662, Slicer#4664
@Sunderlandkyl Sunderlandkyl mentioned this issue Mar 30, 2020
Merged
@Sunderlandkyl Sunderlandkyl linked a pull request Mar 30, 2020 that will close this issue
BUG: Prevent segment editor error messages on scene close #4788
Merged
Sunderlandkyl added a commit to Sunderlandkyl/Slicer that referenced this issue Mar 31, 2020
@Sunderlandkyl
BUG: Prevent segment editor error messages on scene close
b8c5a3d 
- Modified events are now blocked during parameter node initialization
- Error message is not displayed if no parameter node is found during updateWidgetFromMRML
- More thorough error checking for parameter and segmentation nodes in autocomplete effect

fixes Slicer#4662, Slicer#4664
Sunderlandkyl added a commit to Sunderlandkyl/Slicer that referenced this issue Mar 31, 2020
@Sunderlandkyl
BUG: Prevent segment editor error messages on scene close
42c7057 
- Modified events are now blocked during parameter node initialization
- Error message is not displayed if no parameter node is found during updateWidgetFromMRML
- More thorough error checking for parameter and segmentation nodes in autocomplete effect

fixes Slicer#4662, Slicer#4664
Sunderlandkyl added a commit that referenced this issue Mar 31, 2020
@Sunderlandkyl
BUG: Prevent segment editor error messages on scene close
c339aab 
- Modified events are now blocked during parameter node initialization
- Error message is not displayed if no parameter node is found during updateWidgetFromMRML
- More thorough error checking for parameter and segmentation nodes in autocomplete effect

fixes #4662, #4664
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Sunderlandkyl Sunderlandkyl

Labels
Priority: Low Small, non-essential improvements or fixes Type: Bug Something isn't working correctly
Milestone
Slicer 4.13
Development

Successfully merging a pull request may close this issue.

BUG: Prevent segment editor error messages on scene close Sunderlandkyl/Slicer
3 participants
@lassoan @Sunderlandkyl @slicerbot