Hi Jose,
1) We recommend to build in release mode for installers. Side note: at least on Windows that’s the only configuration we support for building installers. However, we received reports that MITK feels slower for some users now compared to v2016.11. This is probably related to the update of the VTK rendering backend to a modern OpenGL backend that is a little bit more demanding regarding minimum graphics hardware specs. Even if a graphics card is quite powerful but old, we found that the cheapest but new graphics cards run way better. 2) You can hide the logging console window (on Windows) by setting the MITK_SHOW_CONSOLE_WINDOW variable to OFF in CMake. There should be an integrated log view (MITK_BUILD_org.blueberry.ui.qt.log). 3) We recommend to use either 128x128 PNGs or even SVGs for icons. When using SVGs, make sure that the virtual resolution of the files is not larger than something like 512x512 as Qt will draw the vector graphic on a canvas of this size and huge resolutions can lead to trouble. 4) This is currently an active topic internally and we’re planning to come up with a nice customizable solution. What you currently see is a DICOM id (series id I think, not sure about this). Best, Stefan From: José Alonso Solís Lemus [mailto:alonso.jasl+...@gmail.com] Sent: Tuesday, August 20, 2019 12:35 PM To: mitk-users@lists.sourceforge.net Subject: [mitk-users] [MITK v2018.04.2] Apparent performance issues in newer MITK version Hello MITKers, We have developed an app running on top of MITK 2018.04.2 as an extension project. The project builds perfectly fine. Apart from a tiny bug (https://phabricator.mitk.org/T26451) that's already been reported by us we have been able to distribute it to the people using it. We have received some feedback from our users plus we have some minor inquiries I have not been able to find in the documentation. I thought better to include them all in the list them below: (1) "The app feels slower / more sluggish". I wonder if there is anything we could do to improve the user experience? Perhaps building the app in Release mode? Did you get any performance difference from MITK 2016 to now? (2) The Logging view is very useful, is there a way to put it in the main interface (similar to the DICOM button at the top of the UI)? (3) I've noticed resolution of the elements in the ui (labels in buttons and symbols) appear blurry, with poor resolution. I compared it to your binary release of the MITK Workbench, and the difference is evident. Any idea why could this be the case? perhaps an option when building? (4) When importing a DICOM file, the name is not displayed in the task manager, instead a string of numbers is shown. I'm told this is not a usual behaviour. Thank you for your help! Kind regards, Jose Alonso
_______________________________________________ mitk-users mailing list mitk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mitk-users
