Result of the discussion:
At the current state we voted against moving to core.

Result of the discussion:

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

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

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.

@hentsch / @kislinsk : Shouldn't we already set QmitkPlotDialog/QmitkPlotWidget/QtHistogram to deprecated then. To give us sooner then later the posibilite to realy remove the code from the codebase. If I see it correctly, that would also gives us the possibility to reomive Qwt as a third party package from MITK. What do you think?

Pushed new branch T25941-Improve_mapper_view_user_manuel.

@kislinsk Thanks for the hint.

I have concerns with the latest commit. See comments there. You can come by and ask if you have any questions.

The fix is not good and has several problems. See comment above. If it is not clear how to handle it properly, just drop by an I can explaine.

@kislinsk Stefan, you said you reworked this pragma for MITK? Does it implie any changes for 3rd party projects?

Pushed new branch T26287-Perfusion_crash_when_converting_signal.

It seems to beeing correlated with the addition of the generated concentration node to the data storage. If the nodes are not added to the datastorage, I cannot provoke a crash. This is at least concistent to the finding that there is also no proplem if we calculate the concentration beforehand.

Narrowed down the point where it crashes.

Pushed new branch T26265-Connect_error_multinodeselectionwidget.

Pushed new branch T23808-Image2ImagePropertyRelation.

😄

Can you reproduce your problem now with the fix, that helped me out?

Pushed new branch T26219-Crash_by_selection_widget_after_close_project.

Found it.

OK, I have narrowed it further down.

@kalali @kislinsk , added you two has you have some experience with at least either rendering/mapper or selection concept. May be you have additional ideas.

The problem occured in context of selection widgets and may be could be patched for selection widgets in context of T26218.

This assumption was incorrect :(. Even if the widget properly release the node if it is deleted the problem still occures?!?

The callstack as additional information:

Pushed an implementation for option 2. Widgets are now synced and remove selections that are not part of their datastorage any more.

Pushed new branch T26218-Sync_node_selection_widget_with_datastorage_node_delete.

Uh oh, that was fast. ;)
I hadn't even made up my mind on that matter. My first purpose was to open up the discussion on that topic...

If you have already an interim branch, could you push it, just to be sure that it doesn't get lost.