Address issues related to integration with VTK 9.1

[jcfr]

The following content was copied from #90 (comment)

---

(1) Retrieval of last position associated with generic tracker

Retrieval of last position associated with generic tracker in
vtkVirtualRealityViewInteractor::GetTrackedDevicePose given
the index is not possible.

⚠️ TODO: Handle retrieval of tracker position associated with generic tracker associated with index.

• ✔️ This is expected to be fixed following the integration of these pull-requests:
  • Fix retrieval of OpenVR last post updating VTK #103
  • COMP: Fix build using renamed API to retrieve OpenVR pose #104

Background:

Add support for generic tracker originally contributed in these commits:

• Kitware/VTK@6083532cf8 (ENH: Exposing the generic tracker openvr device type to downstream projects)
• 59b7d1bf3 (Adding interface and logic to maintain MRML transforms for each generic VR tracker)

but removed following the refactoring done in these commits:

• Kitware/VTK@1aac3fe5f (Create VRInteractorStyle and VRRenderWindowInteractor)
• Kitware/VTK@af0fab486 (Clean up VR and OpenVR classes)
• Kitware/VTK@9bd64d666 (Cleanup and rework of the VRInteractorStyle and subclasses)
• Kitware/VTK@09a478a22 (Cleanup VR camera code and subclasses)

(2) RecognizeComplexGesture is not virtual anymore in base VTK class

⚠️ TODO: Assess with this function should still be overriden with VTK 9.1

Background: The function became non virtual in Kitware/VTK@af0fab486 (Clean up VR and OpenVR classes)

API changes

vtkEventData API changes:

• vtkEventDataButton3D -> vtkEventDataDevice3D

RenderWindow API changes

• GetNumberOfTrackedDevicesForDevice -> GetNumberOfDeviceHandlesForDevice
• GetTrackedDeviceIndexForDevice -> GetDeviceHandleForDevice
• GetTrackedDeviceModel -> GetModelForDevice
• GetTrackedDeviceIndexForDevice -> GetDeviceHandleForDevice

InteractorStyle API changes

• PositionProp sinature updated to include "lwpos" and "lwori"

[cpinter]

I just got around to try the latest versions. The biggest issues I encounter are:

• Continuous error logging DelegateInteractionEventToDisplayableManagers: Unrecognized device in the console. I debugged into it a while ago and there was no apparent easy solution. More work is needed.
  Edit (@jcfr): Most likely fixed by BUG: Fixes issue on Oculus that throws error constantly when used #99 contributed by @aWilson41 ✔️
• Volume rendering does not show up in VR, but models/segmentations do. I confirmed that on the same machine/configuration volume rendering shows up with Slicer 7da00248941292c429ba11204d3a5a7d78210a46, but not after the VTK update. I'm not sure how to approach this problem other than checking if the displayable manager is properly registered (which I'll do shortly).
  Edit (@jcfr): Most likely fixed by BUG: Update VTK to include OpenVR/OpenXR volume rendering fix Slicer/Slicer#6584 ✔️

[cpinter]

@lassoan had the idea to check if volume rendering shows up with CPU rendering. It does not.

[lassoan]

Sometimes you need to disable and re-enable depth peeling to make volume rendering show up. Does it help?

You can also try to disable volume rendering in all views except in the VR view, add breakpoints in the volume rendering mapper and see if it gets called.

[cpinter]

Sometimes you need to disable and re-enable depth peeling to make volume rendering show up. Does it help?

You can also try to disable volume rendering in all views except in the VR view

These two didn't work. I'll debug into the mapper once the build succeeds (but on the VR computer the debug build failed many times due to an external data timeout. I updated and started the build again. Update: it keeps failing, this time with this download, the interesting part is that from the browser I can download it but the build always fails on one or another)