Thank you very much for the reply and for the examples provided. Work on this project had grinded to a halt due to other competing priorities, but has emerged back to the forefront.
Hence, I would like to pose some follow-up questions:
This is somewhat of a sanity check, but my understanding is that the
vtkCollisionDetectionFilteris not a standalone function, i.e., given that it does not seem to be integrated into VTK, I cannot simply call it as I would for say, model creation (e.g.
Rather, it seems to me that I will have to clone the repo referenced (
SlicerRT/SlicerRtCommon), containing all the relevant scripts and files of the
vtkCollisionDetectionFilter, and then source them into my project (as was done by the
RoomsEyeViewmodule). Is my understanding correct?
The scripts and functions comprising the
vtkCollisionDetectionFilterare written in C++, as was the
RoomsEyeViewexample module sourcing it, hence simplifying integration and function calls to collision detection features.
However, my code framework as described in my original post (i.e. consisting of widget instantiation of drop-down menus, sliders, event handling, and population of the Slicer scene with geometrical objects) is written in Python.
As such, this poses integration challenges as I will need to make calls to the C++
vtkCollisionDetectionFilterfunctions from my Python framework. I have looked into invoking Python bindings such as
SWIG, but such translation schemes seem somewhat intimidating to a novice like me.
Hence, I am wondering whether there may be a simpler solution that will allow me to leverage the
vtkCollisionDetectionFilterfunctions (written in C++) into my Slicer programming development work that has been done in Python.