Deleted branch from rMITK MITK: bugfix/T29350-NodeSelectionDialogNeedsMarginAndSpacing.

Pushed new branch to rMITK MITK: bugfix/T29350-NodeSelectionDialogNeedsMarginAndSpacing.

"Clear Contour" is a good propsal that should be changed.

It works on Windows and Ubuntu. The default hotkey for reinit is Ctrl+R and can be specified in the preferences. Maybe Ctrl+R has already a special meaning on macOS. We need to check but I would classify this task as cleared for further investigation.

I recreated the problem by loading any image (the described ones work, as well as just Pic3D.nrrd) and moving the level windows really far (either by dragging the bar to one direction, or moving it back and forth to the upper and lower bounds), to values around the scale of 4e+38. At that point, the workbench just freezes and stops responding.

The images mentioned in the checklist are:

Since this cannot be reproduced right now, we assume this was caused by user error, maybe clicking at the wrong location. For the upcoming release there won't be anything done about this.
In the long-term, we will have to think about if we want to try and improve level window UX, especially in regard to the MxN multi-widget view (T28578) which may need fundamental changes.

We think that people in the real world do not use the smoothing options at all and checking for their impact revealed that they seem to have no effect at all in most cases. We decided to remove the options from the preferences. In addition, there's a message in the terminal when no smoothed mesh could be created which is the case for some single-slice segmentations. It even suggests to try again without smoothing. However, this should probably be a more prominent feedback as message box for example.

Pixel information has been removed. To add a specific view for pixel information, see T29324: Create view for pixel information.

Pixel information has been removed with {D686}. We discussed that we will open a new task to add a simple pixel value information view as a separate task.

Deleted branch from rMITK MITK: feature/T28607-live-wire-improvements.

Should be resolved with the changes introduced with the lasso tool reworks. Lets wait for tester feedback.

I connected this task with D686: Not all discussed points are handled here but I removed the UpdateStatusBar-functions completely and added a simple function to update the status bar info with the mouse pointer / world position and the global time dynamically.
More code changes will be uploaded to provide ideas on how to show image pixel information.

In T25043#239851, @kalali wrote:

1. Do we agree that there will be no position / pixel value information shown in the status bar?
   1. or are we only talking about the (maybe case-specific) pixel value information; meaning the position / index should still be shown in the status bar?
   2. if everything should be removed from the status bar, we wouldn't put any new functions in the "StatusBar"-class, right?

I would say A. So coordinate information is still visible.

I worked on related topics last week and found some solutions for this problem (and also solving the parent task).
Some questions remain, though:

Close this task. As the "classical" overwrite checkbox is dropped. Region Growing has to be written completly new anyways and then based on mitk::SegToolWithPreview, such features will come for free.

Pushed new branch to rMITK MITK: feature/T27319-multilabelInterpolation.

Deleted branch from rMITK MITK: T27100-Revise-DataManager-Plugin-Documentation.

Deleted branch from rMITK MITK: T27100-Develop-integration.

We updated the checklists.

@kahl So are you working on this? If not, could you remove yourself as the assignee of this task?

I tested this with the related review and the fix c042953a0088 solves this issue.

Related: T29088: [Checklist] 3D Segmentation - Checklist and MITK UI Inconsistencies