Hi Aashish,
Actually I thought that vrpn was somehow working as a universal
interface layer between different devices and the software using them
(for example paraview). Using vrpn client to test the data, my device
(WintrackerIII), sends the proper 3 values for the position,I convert
them in meters after reading them from the usb and vrpn seems to see
them correctly, so I was expecting it to feed paraview with the proper 3
values describing the x,y and z positioning. Doesn't the property
require 3 double value components?
Do you know what those 14 arguments displayed in my error represent?
Best,
Emiliano
Il 10/01/13 00:45, Aashish Chaudhary ha scritto:
On Wed, Jan 9, 2013 at 10:50 AM, Emiliano Pastorelli
<[email protected] <mailto:[email protected]>> wrote:
f arguments i listed in the erro
I think we don't check if your sensor has number of components equals
to number of components required by the property. I think we should.
So if your sensor has only one component then it will fail at run
time. Now if that's the case then you need to create a new interactor
style that can conver a 1 component data to 3 component data.
Let me know if I am missing some information.
Hope it helps,
Aashish
--
| Aashish Chaudhary
| R&D Engineer
| Kitware Inc.
| www.kitware.com <http://www.kitware.com>
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
