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

Various traceback errors when closing scene after using Segment Editor #4662

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

Various traceback errors when closing scene after using Segment Editor #4662

slicerbot opened this issue Mar 13, 2020 · 0 comments · Fixed by #4788
Assignees
Labels
Priority: Medium Issues that we plan to fix but there are available workarounds
Milestone

Comments

@slicerbot
Copy link
Collaborator

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.

@sjh26 sjh26 added this to the Slicer 4.11.0 milestone Mar 18, 2020
@sjh26 sjh26 added the Priority: Medium Issues that we plan to fix but there are available workarounds label Mar 18, 2020
Sunderlandkyl added a commit to Sunderlandkyl/Slicer that referenced this issue Mar 30, 2020
- 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, 4664
Sunderlandkyl added a commit to Sunderlandkyl/Slicer that referenced this issue Mar 30, 2020
- 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
- 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
- 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
- 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
Labels
Priority: Medium Issues that we plan to fix but there are available workarounds
Development

Successfully merging a pull request may close this issue.

3 participants