- User Since
- Aug 1 2016, 12:10 PM (154 w, 4 d)
@kompan: Could you be so kind and take care when you have some time left? Thanks!
@kompan: Could you be so kind and take care when you have some time left?
Thu, Jul 11
@kislinsk Shouldn't we raise priority, if we run otherwise in a licesnsing gray zone?
Tue, Jul 9
Jun 17 2019
May 29 2019
May 24 2019
It affects every branch that containes the ModelFit module and tries to build it with VS 2017 >=15.9.11
May 23 2019
May 22 2019
May 20 2019
May 17 2019
Result of the discussion:
At the current state we voted against moving to core.
Result of the discussion:
May 11 2019
Code coverage can be checked now.
And everything is setup up to use it with codecov.io
May 10 2019
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).
May 9 2019
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.
May 2 2019
@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?
Apr 29 2019
Pushed new branch T25941-Improve_mapper_view_user_manuel.
@kislinsk Thanks for the hint.
Apr 26 2019
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.
Apr 24 2019
@kislinsk Stefan, you said you reworked this pragma for MITK? Does it implie any changes for 3rd party projects?
Apr 18 2019
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.
Apr 17 2019
Apr 15 2019
Apr 12 2019
Pushed new branch T23808-Image2ImagePropertyRelation.
Apr 5 2019
Can you reproduce your problem now with the fix, that helped me out?
Pushed new branch T26219-Crash_by_selection_widget_after_close_project.
OK, I have narrowed it further down.
Apr 4 2019
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...