Mar 29 2019
Jun 27 2018
Jan 20 2017
This bug still occurs on my system!
Aug 26 2016
Aug 24 2016
Aug 23 2016
I added a find package openssl to the CMakeLists.txt of the xnat plugin. If openssl can not be automatically found (which is likely for windows), you can set LIB_EAY_RELEASE to your libeay32.dll and SSL_EAY_RELEASE to your ssleay32.dll and they will be automatically:
- copied to you binary directory
- copied to the installer directory if an installer is build
Aug 22 2016
@espak Do the changes merged in rMITKc3d09f20 fit your requirements? You can switch between hierarchy changes being allowed or not in the datamanager preference page (bottom checkbox).
Aug 12 2016
This problem still occurs when building a package both for Qt 5.6.1 and Qt 5.7.0.
The only way to make the Workbench start is to manually copy the the QtWebEngineCore.framework from <QtPath>/lib/ to the MitkWorkbench.app/Contents/Frameworks/
Aug 10 2016
According to QTBUG-50155, this bug is resolved. We should check that and increase the minimum required Qt version to 5.6.1.
I cannot find the properties in the latest release despite the merges. Did I miss something here? :-)
I also noticed that the annotation font family is not working, italic is actually bold, and bold does nothing.