Deleted branch T22064-Fix-test-for-new-uppercase-DICOM-tags.
- All Stories
- Advanced Search
- Transaction Logs
Sep 10 2020
Deleted branch T19933-Turn-off-outline-of-segmentation-integration.
Deleted branch T22064-Convert-DICOM-hex-tags.
Deleted branch T19933-Turn-off-outline-of-segmentation.
Deleted branch T19933-Outline-of-segmentation-fix-rebase.
Deleted branch T19933-Outline-of-segmentation-fix.
Deleted branch T19609-integration-branch.
Deleted branch T20223-RGBAImageFix.
Deleted branch T19801-planar-figure-interactor-crash.
Sep 1 2020
Hi there! 🙂
Jul 18 2018
Jul 9 2018
Jul 6 2018
Please don't priorize or move tasks on workboards on your own. The workboard is outdated and priorizing will lead to the opposite effect that the task is implicitly burried without a single MITK developer noticing this new tasks among the other hundreds of tasks.
Jun 27 2018
Sep 29 2017
installing all 4 packages solved the problem :)
Jul 5 2017
May 30 2017
May 15 2017
Thanks for the hint. It turned out in the end that the default cubic interpolation simply messed with labels on the rotated view planes...
May 12 2017
Maybe the rotation matrix is not set for the clipping plane? Just guessing...
Thanks for the clarification, that explains the rotation of course. We are having problems with some other tools (e.g. with the clipping plane plugin) that came up just in these cases with (permuted) non-unity matrices. Apparently, that is then unrelated with these fixes.
What do you think is wrong? It looks correct to me.
In some cases, the fix leads to unexpected results (see attached). That is, re-init / global re-inits cause image rotations.@Miklos, maybe you have an idea where to start fixing this issue?
Mar 29 2017
No problem. Closing.
No there is no specific reason.
The target_link_libraries was legacy code and we weren't aware that it could done like you proposed.
Is there a specific reason you are using
This is our module cmake file.
Ok I understand that, but my problem is something else.
I disagree a module not being build should not be an error, as there is currently no way to select which modules are being build. Instead all that can be build are by default. Switching to an error would result in just about no build ever being possible.
Mar 28 2017
Feb 6 2017
Feb 3 2017
Pushed new branch T22465-merge-release-into-master.
fixed by T22463
Pushed new branch T22463-update-MatchPoint.
I reverted this and merged it to master. Fixes Ubuntu 16.04 Clang build and doesn't break 14.04 , so maybe this could be included in the release? @goch @kislinsk ;)
We added a Mutex to lock access to m_StatisticsImage to make sure it is not set to nullptr while the calculation thread is still using it to calculate the statistics.
Pushed new branch T22450-chrash-in-calculation-thread.
Pushed new branch T22454-MultiSegmentationIcons.
Pushed new branch T22451-add-webengine-translations.
did you check that the old mbi homepage http://www.dkfz.de/en/mbi/index.php isn't referenced anywhere? It's used in the about dialog.
Pushed new branch T22442-documentation-updates.
We currently do not copy the Qt/5.7/msvc2015_64/translations/qtwebengine_locales directory into our installer. Thus it does not find it when looking for it. This was mainly done, because we do not offer any locale but english anyway, but it was pointed out, that it might be useful for third party developers who localize their own application.
Feb 2 2017
Addition to the previous fix in D34.
The 3D+t problem should now be fixed. However, my solution is by no means an elegant one.
Pushed new branch T22412-prevent-regiongrowing-timestep-crash.
I guess the issue arises from the fact that VTK uses OpenGL 1.x and QWebEngine uses modern OpenGL (>= 3.2). macOS in particular has trouble with OpenGL contexts of different versions in a single application. That's why I would suggest to wait for the VTK OpenGL 2 backend upgrade for MITK, which uses OpenGL 3.2. Together with QSurface::defaultFormat() we should be able to ensure OpenGL contexts of the same compatible version.
Pushed new branch T22442-Housekeeping-Master.
Feb 1 2017
For me a multi component crash does not happen anymore.
For 4D images the crash occurs in
returning a nullptr, as GetTimeGeometry() only has a single timestep even for 4D images.
Pushed new branch T22442-Housekeeping.
Has been fixed with D33.