VTK/3DConnexion Devices Support: Difference between revisions

From KitwarePublic
< VTK
Jump to navigationJump to search
Line 22: Line 22:
* <tt>VTK_TDX_INCLUDE_PATH</tt> to point to the path of <tt>xdrvlib.h</tt> (without mentioning <tt>xdrvlib.h</tt>)
* <tt>VTK_TDX_INCLUDE_PATH</tt> to point to the path of <tt>xdrvlib.h</tt> (without mentioning <tt>xdrvlib.h</tt>)
* <tt>VTK_TDX_OBJECT_PATH</tt> to the full path to <tt>xdrvlib.a</tt> (mentioning <tt>xdrvlib.a</tt>)
* <tt>VTK_TDX_OBJECT_PATH</tt> to the full path to <tt>xdrvlib.a</tt> (mentioning <tt>xdrvlib.a</tt>)
=== Windows ==
=== Windows ===
Easy. There is nothing else to set.
Easy. There is nothing else to set.
== Build VTK ==
== Build VTK ==
Just build vtk.
Just build vtk.

Revision as of 18:12, 21 August 2009

Support for 3DConnexion Devices (SpaceNavigator, SpacePilot) inside VTK

THIS IS EXPERIMENTAL WORK

Naming convention

We pick the name TDx to refer to classes or types to support 3DConnexion Devices. "T" stands for "Three", "x" stands for "connexion". Why? because 3DConnexion calls its software 3DxWare but we cannot have types and classes starting with a number in C++, so we chose "T" instead of "3".

How to use it

Install the 3DConnexion Device driver

Linux

Windows

Easy. Nothing to add about it.

Install the 3DConnexion SDK

Linux

Windows

Easy. There is nothing to install

Configure VTK

Launch cmake and set VTK_USE_TDx to TRUE

Linux

Set the advanced variables:

  • VTK_TDX_INCLUDE_PATH to point to the path of xdrvlib.h (without mentioning xdrvlib.h)
  • VTK_TDX_OBJECT_PATH to the full path to xdrvlib.a (mentioning xdrvlib.a)

Windows

Easy. There is nothing else to set.

Build VTK

Just build vtk.

Test it

Launch TestTDx in interactive mode 1. Get the full command line of the test with:

$ ctest -R TestTDx -V -N

2. Copy the full command line in the prompt and add -I at the end, to run the test in interactive mode

3. Enjoy

Linux

Windows

Mac

empty