hi renan, i did this with eric wing for a client of ours. we only did it for mac os x, because the packaging was easiest. we decided against the windows stuff for the reasons paul mentioned.
bob On Apr 3, 2008, at 3:01 PM, Paul Martz wrote: > Hi Renan - > > I looked at adding support for this device to OSG, but was put off > by the fact that they have per-platform SDKs. I think Mike Weiblen > was looking at adding this into VRPN. > > Anyhow, why not just derive a new class from MatrixManipulator and > add that to the viewer? Then hide all your device-specific code > inside that class. You'd need to attach your manipulator before > calling run() of course. > > Paul Martz > Skew Matrix Software LLC > http://www.skew-matrix.com > +1 303 859 9466 > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > ] On Behalf Of Renan Mendes > Sent: Thursday, April 03, 2008 12:23 PM > To: OSG Mailing List > Subject: [osg-users] New Device Input > > Hi, > > I'm working on a project that requires the use of a new input > device, called space navigator. I have the method that gets the 6 > coordinates from it. I'd like to know how to get it at every frame. > I thought of using a callback, but it doesn't seem right, for the > object from that class is not conceptually a osg::Node. Can I > include it in my viewer.run() ? > > Thanks for your tip, > > Renan M Z Mendes > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
