> Exzcuse my lack of knowledge, but what sort of input device generates
> color data? All of the sensors that I know generate 3D spatial coordinates
> and hence |Transform3D is the perfect choice. .
For me an InputDevice is a piece of HW (or SW) which delivers a bunch of values. How
these values are interpreted is quite application specific (sure it makes sense for
head tracking equipment or arm tracking equipment, but not necessaryly for a
joystick).
> If you need something more, why
> not extend the T3D class with your own extra data?
As far as I understood the documentation does the sensor class an automatic
transformation according to some hot spot. These extra calculations is not necessary
in some cases. Also I think that the values of the Transform3D will be copied in the
Sensor class. This are also extra operations not needed then.
> Having it return aything else could cause other problems. The principal one is
> that for generic InputDevice implementations for use by Joe Public
> would cause errors with the behaviour scheular where it automatically
> drive head tracker movement in J3D.#
What generic InputDevice implementations exists ? And why should they automatically
drive head tracker movement ?
I'm sorry but I didn't quite catch what you mean with the sentence containing Joe
Public, certainly because I'm not a native speaker. Can you pls. explain what you
mean ?
regards Paul
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
