I forgot to enable the segmentation plugin... I'll test it tomorrow.

I can reproduce it. I did exactly the steps in the task description. I used MITK.2018.4.0 installer. I'll check on a (more or less) current master.

Wait for it...

I couldn't reproduce it. @kleina Can you? (maybe it occurred only due to missing reinit?)

@kausch What's the status on this task?

Pushed new branch T26252-BoostInstallError.

I really tried but I was not able to reproduce this issue. For example, I created a segmentation and clicked multiple times on "Create smoothed polygon model" and "Create polygon model". Worked every time. I then created another segmentation in the same scene and did the same there with the same results.

Pushed new branch T25522-MasterIntegrationBranch-13-05-2019.

Code coverage can be checked now.
And everything is setup up to use it with codecov.io

Pushed new branch T25832-migrateModelFit2019-05.

Pushed new branch T26324-optimizeZoomingOption.

Pushed new branch T25871-fix-unsigned-int-comparison-warning.

Pushed new branch T19683-ShowOnlySelectedNodesCrosshairVisibilty-baseRenderer.

I think it would be nice but is no show stopper, because we could, as a work arround, use a chartline that only contains the highlited point(s).

T26323 is needed to highlight the current point

Feedback from @floca:

1. Der Titel der X-Achse und die Achsenbeschriftungen liegen über einander und sind deshalb nicht zu lesen.
   • is already fixed with T26274, but not yet in this branch
2. Fixed Scaling (für X und Y) funktioniert nicht richtig.
   • true
3. In der Methode OnFullPlotClicked ist ein Task (T26222) referenziert, den es gar nicht gibt. Vielleicht ist das aber jetzt auch schon durch meinen Fix erledigt.
   • code was deleted, works fine
4. Kritische Regression gegenüber dem alten Widget: Im Moment flackert es immer sobald man die Achsen anpasst oder (noch schlimmer) wenn man einen neuen Punkt ansteuert. Dass ist insbesondere beim explorieren von Daten nicht gut, da es leicht laggt und sehr irritiert.
   • opened T26320
5. Kritische Regression gegenüber dem alten Widget: Im Moment aktualisiert sich der Plot erst wenn man die Maus wieder loslässt (wenn man im SliceNavigator oder direkt im Bild neue Punkte anfährt). Früher wurde automatisch immer gleich mit aktualisiert, es wäre sehr gut, wenn das wieder so wäre. Entsprechend müsste der Chart neugemalt werden, jedesmal wenn die Positionsänderung propagiert wird. Im Moment sieht es so aus, als würde gewartet, bis der Main-Thread idelt.
   • can't reproduce. The update takes a while (probably because of new painting of the widget), but has nothing to do with mouse click release. @floca we should look again if T26320 is fixed.

We reverted the changes according to your concerns. Instead of creating a new ImageStatisticsObject in the GetStatisticsForTimeStep method, we now check whether the time step exists before calling the method. That fixed the problem. Statistics are now only shown for the time steps that have a segmentation associated with.

To get an overview of MITK subprojects:

Pushed new branch T25871-chartTypePie.

Without a fundamental rework of the rttb build mechanics the only way to sooth the problem is to explicitly check if all prerequisits are fullfilled and if not give a meaningfull cmake error message.

Pushed new branch T25882-CDash-v2.6.

This would be favorable. However, if we deprecate the QmitkPlotDialog/QmitkPlotWidget/QtHistogram classes, this leads to warnings (and errors because of warnings-as-errors).
@kislinsk do you see a possibility?

@hentsch Is the one time step segmentation applied to all time steps? What is the expected behavior?

Things I found so far:

This task is not valid anymore.

1. The level window slider has an option to modify the level window of a (list of) selected node(s) (see T25483)
2. The BlackSwan project uses the PACS mode where the level window can be changed via mouse buttons
3. The render window manager now uses the concept of data storage inspectors and thus behaves differently than here