Hi Matt,
So why are the manipulators currently set up the way they are? and would the
community benefit from a new idiom and class structure in this particular area?
If you guys agree with my point, I may try to develop such a structure.
I totally agree with the principle. The reason is probably just the
classic "historical reasons" and "we've never needed that before" ones
that are part of open source, incremental, evolving development.
Now that the camera manipulator API is already different between OSG
2.8.x and SVN, now might be the right time to do what you suggest.
What would be the idea specifically? Would the camera manipulators
expose a series of input connections, say "pitch up/down", "throttle
up/down", and then have an InputDevice class that would expose outputs
that you could connect to the camera manipulator's inputs?
I would suggest that axes be mappable to either an analog axis (say
mouse up/down or joystick y axis) or a pair of buttons (one for
incrementing and one for decrementing the value).
J-S
--
______________________________________________________
Jean-Sebastien Guay jean-sebastien.g...@cm-labs.com
http://www.cm-labs.com/
http://whitestar02.webhop.org/
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
