Hi,
from what I see a reinit is called as soon as MVClipper is added to the scene. I do not know how this is done in your code but I recommend to look around the code location where MVClipper is added to check if you do an explicit reinit. For example, in vanilla MITK, when I open a surface, reinit is called. However, when a plugin creates and adds a surface like the 3d interpolation, reinit is not called. Also in your application several objects were added to the scene during the video after the crosshair rotation without any reinit. Best?, Stefan ________________________________ Von: José Alonso Solís Lemus <alonso.jasl+...@gmail.com> Gesendet: Montag, 2. November 2020 15:20 An: mitk-users@lists.sourceforge.net Betreff: [mitk-users] [MITK v2018.04.2] Coupled crosshair rotation resets before expected Hi, We develop our cardiac imaging research app on top of MITK v2018.04.2. Our users noted to us that at a point in the pipeline where the coupled crosshair rotation is needed, the rotation resets to orthogonal view automatically. This is difficult for them, as they need to verify in the correct orientation that their input has produced a good result. I think you will understand the problem much more if you see a video of it. We have a tutorial video for our users where the error can be seen. You can go to this website (cemrgapp.com<https://cemrg.com/software/cemrgapp.html>), and click on "video manual 1", or you can try with this link<https://cemrg.com/software/scar-video1.mp4>. Below I'll describe the times when the issue is happening so you don't have to watch everything: 6:03 - 6:13 :: the process in the pipeline is started and the coupled crosshair rotation is done. 6:42 - 6:50 :: points are selected with the special orientation 6:50 - 6:51 :: The view is reset to orthogonal HERE. Normally, the view would not reset and our users would have a chance to check whether the sphere generated is covering the right volume of the atrium. The video shows an example case, where no correction is needed. This did not happen in MITK v2016.11, so I assume it was added as a feature? Is there a way to programatically store the rotation? If there is, that would be the ideal workaround for us. Otherwise, I would appreciate some guidance as to how to address this issue. Many thanks, Jose
_______________________________________________ mitk-users mailing list mitk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mitk-users
