Issue 39 in vrjuggler: Enhancement Request: Intersense API driver search for isense shared library alongside the jconf
vrju...@googlecode.com
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 39 by ryan.pav...@gmail.com: Enhancement Request: Intersense API
driver search for isense shared library alongside the jconf
http://code.google.com/p/vrjuggler/issues/detail?id=39
It would be great if the Intersense API driver (and actually, more
generally, any jconf-configured component that loads additional assets,
like audio files for sonix) could look in the directory that contained the
jconf loading it. Installing the dll on all machines in the search path
isn't really a great option (and not an option for audio files), and
absolute paths in the jconf files are liable to break easily.
vrju...@googlecode.com
Labels: -Type-Defect Type-Enhancement
Comment #1 on issue 39 by patrick....@gmail.com: Enhancement Request:
Intersense API driver search for isense shared library alongside the jconf
http://code.google.com/p/vrjuggler/issues/detail?id=39
Have you investigated the practicality of this enhancement? I can
definitely see the value, but I am not sure how well it can be made to work
with the current design. The first option that comes to mind is that every
jccl::ConfigElement would have to know the path to the file from which it
was loaded.