Proximity Toolkit Future Work

<< Back to Proximity Toolkit


  • Change all instances of "Volume" to be "Feature" instead.
  • Use "Subject" to described TrackedPresences. Reserve "Presence" to mean anything physical in the space, ie. Features, Devices, and Subjects.

Proximity Toolkit Library

  • Expand the LocationDecorator to contain optional Marker information.
  • Create a CollisionDecorator that contains the collision volume of the presence.
  • Better decoupling from System.Windows.Forms (required for Screen) and System.Drawing (required for Point/F, Rectangle/F, Size/F) libraries.
  • LocationRelationArgs indexable by Marker name, much like the PointerRelationArgs.
  • Merge all Rotation functionality with Orientation. Provide indexing possibilities to handle segments and joints. Remove Pose decorator.
  • MotionDecorator should be able to represent rotational motion as well, calculated by averaging the angle differences of all pointers between subsequent data frames.
  • A mechanism so that Input Modules can define their own custom decorators, and client programs can access those decorators with a reference to the Input Module's .dll file. I tried doing this by putting the custom decorators into the ProximityToolkit.Presence namespace (which is the same namespace that the standard decorators from the ProximityToolkit are in), however because it is in a different assembly, my code for instantiating the decorators by name (in TrackedPresence.OnDispatchUnhandled) could not create an instance of the custom decorator.

Proximity Server Application

  • Finish or elaborate on relation visualizations.
  • Visualization of session playback.
  • Automatically reload Vicon Skeletons when VSK path is changed. Currently a restart of the program is required.
  • Sleep mode when minimized and no clients connected, to minimize CPU usage when not being used.

Vicon Input Module

  • Add ability to define collision volumes from VSK editor, and save data in VSK file.