Recently, there has been some integration of VTK into the QGraphicsView mechanism (http://prashanthudupa.livejournal.com/48221.html).
This may allow for a seamless coexistence of (interactive & transparent) Qt Widgets and the VTK/MITK Rendering Pipeline.
Due to the almost completed work to re-enable a Qt independent rendering of MITK (see T4735), the above mentioned "vtkQtGraphicsViewRenderWindow" could be combined very straight forward with MITK.
In principle, all I did was to pass the vtkQtGraphicsViewRenderWindow as parameter to the constructor of the new QT-independent mitk::RenderWindow.
Attached, you can find:
- A patch for the current OS-MITK including the above mentioned class, few minor modifications to rendering, and an adapted tutorial step 3
- A screenshot of the step3 example showing an opaque widget in front of a MITK rendering, interaction of both, the widget and the rendering is working (although there is a crash on application exit in vtkMitkEventProvider)
To discuss/to investigate:
- (How) does the Qt-initiated re-renderings affect efficiency/performance?
- Due to the use of mitk::RenderWindow instead of QmitkRenderWindow, 'interaction-integration' now relies on the new vtkMitkEventProvider?
- What about this change w.r.t. our QmitkTextOverlays and their behaviour on different OSes?
- The role of the vtkQtGraphicsProxyWidget and its implementation
