New remote branch pushed: bug-15369-CrashOnNodeDeletion

The minimal code change for the crash prevention, however not the 'best' solution.

For 2d interpolation, the whole InterpolationWidget is disabled after the node is removed from datamanager, this somehow does not work in case the 3D interpolation is enabled. De-activating the interpolation widget in the same manner would be the desired fix.

[ Resetting status and assignee ]

New remote branch pushed: bug-15369-crash-on-accept-3d-interpolation

[d4af86]: Merge branch 'bug-15369-crash-on-accept-3d-interpolation'

Merged commits:

2013-06-23 01:54:30 Andreas Fetzer [904fd1]
Deactivating tool if working node becomes invisible

2013-06-23 01:28:20 Andreas Fetzer [0712ff]
Fixed wrong warning label for segmentation

2013-06-23 01:27:50 Andreas Fetzer [d9e7e8]
Only show interpolation result if workingdata is really visible

2013-06-23 01:23:12 Andreas Fetzer [dcb6bc]
Minor improvements

2013-06-23 01:22:52 Andreas Fetzer [128f66]
Adding delete event observer for new segmentations

2013-06-23 01:22:05 Andreas Fetzer [c42a45]
Removing observers in dtor

2013-06-23 01:21:31 Andreas Fetzer [1d41bb]
SurfaceInterpolationController is now listening for delete event of selected segmentation

2013-06-23 01:18:58 Andreas Fetzer [011e3c]
Fixed visibility warning for segmentation

2013-06-23 01:15:59 Andreas Fetzer [906384]
Show or hide 3d interpolation if working node visibility is changed

2013-06-23 01:12:50 Andreas Fetzer [4e66e8]
Made ShowInterpolationResult a public function

2013-06-23 00:53:11 Andreas Fetzer [0a31fa]
Removed unused variable

2013-06-23 00:40:12 Andreas Fetzer [f9ef71]
Disable interpolation widget if working data is null

2013-06-23 00:37:58 Andreas Fetzer [d36373]
Hide previous interpolation when a new contour id is set for the 3d interpolation

2013-06-23 00:37:12 Andreas Fetzer [9f2f21]
Add check for invalid working data when accepting the 3d interpolation

2013-06-23 00:36:21 Andreas Fetzer [4df712]
Some code cleaning