- User Since
- Aug 1 2016, 12:10 PM (133 w, 1 d)
Fri, Feb 15
Hi. I completely agree with your comment. I just implemented a handler to avoid a call to terminate() in my application, but the implementation is incomplete. The main problem, as you commented,, is how are we going to let know the main thread that an exception occurred in the tracking thread. There are several possibilities (it would be great to have Qt signals mechanism here), but I think that we have two main options:
Thu, Feb 7
Aug 28 2018
I can confirm that in version 15.8.1 this is also happening in Debug, without any global optimization. I have already reported this, hope they will fix it soon.
Aug 3 2018
Jul 30 2018
Apr 26 2018
Apr 1 2018
Mar 31 2018
Ok. I've patched my MITK version. HDF5 was using CMAKE_BUILD_TYPE to get the RelWithDebInfo directory. They were also using CMAKE_BUILD_TYPE in other places, and that does not work in multi-configuration generators like Visual Studio. I've downloaded the latest stable version 1.10.2 and this problem is corrected. They are not using CMAKE_BUILD_TYPE anymore.
Mar 29 2018
Jul 25 2017
Jul 17 2017
Jul 15 2017
Jul 13 2017
Jul 12 2017
Ok, I have created a new pull request:
Jul 7 2017
Feb 6 2017
Jan 10 2017
Aug 2 2016
The same issue was freezing the workbench in my nvidia hardware with Qt 5.6.0. I've added the following lines to main():
This is also happening when compiling in Ubuntu x86_64, even with the MicronTracker deactivated. I'm using cmake 3.5.
Some more data:
@Christian Yes, thank you, this solves that issue.
I've collected some more information that changes a little what I've reported before.
For my tests I'm using a mitk::PointSet and a mitk::PointSetInteractor.
Which components may, conceptually, be linked statically? Qt,VTK, ITK, boost, the MITK modules, Blueberry (except for the plugins)?