Skip to content

Latest commit

 

History

History
61 lines (39 loc) · 3.15 KB

README.md

File metadata and controls

61 lines (39 loc) · 3.15 KB

Back to Projects List

SlicerVR: interactive UI panel in the VR environment

Key Investigators

  • Csaba Pinter (Ebatinca, Pixel Medical)
  • Adam Rankin (Robarts Research, Canada)
  • Jean-Christophe Fillion-Robin (Kitware)

Project Description

A key infrastructural element that is still missing from SlicerVR is the ability to show and interact with arbitrary Qt widgets in the VR scene. Up until recently, a blocking issue was an incomplete implementation of the vtkQWidgetWidget class in the VTK version that Slicer was using. Now that Slicer has been migrated to VTK9, the implementation of this in-VR widget continued.

A blocking issue for this to happen is the ability to build the SlicerVR extension against Slicer built with VTK9. Currently, build fails because the build system does not support building VTK remote modules externally (this issue breaks the build of other important extensions as well, such as SlicerVMTK).

Once build is fixed and the in-VR widget is added, arbitrary UI elements of Slicer can be used from within VR, thus basically exposing the entire Slicer functionality within the VR environment.

Objective

  1. Build SlicerVR against VTK9
  2. Add interactive Qt panel to VR scene SlicerVR#43
  3. Make use of the in-VR widget via laser pointer and VR-optimized widgets

Approach and Plan

  1. Update SlicerVR CMake files to build with VTK9
    1. Until a final design for supporting remote modules in VTK is decided, we will build VTKRenderingOpenVR from a separate repository
    2. Extract the said module from VTK proper with history (JC)
    3. Change main CMake file to use this instead of the VTK remote module approach (Adam?)
    4. Fix build issues arising from the switch to VTK9 in SlicerVR (Csaba?)
  2. Try vtkQWidgetWidget in SlicerVR, confirm that it now works (Csaba)
  3. Explore existing possibilities for using a laser pointer emanating from the controllers to control the Qt-based widget (press, click, drag&drop, etc) (?)
  4. Add the already implemented but dormant VR-optimized widgets in the SlicerVR user interface (Csaba)

Progress and Next Steps

  1. Describe specific steps you have actually done.
  2. ...
  3. ...

Illustrations

In-VR user interface

Background and References