Hi Kelvin !
Thanks for the reply and thanks for providing the information about the different
modes of
InputDevice.
> (2) Another factor is the numerically error build up during the process.
>
> In the first method it seems that the transformation matrix is set
> directly using loookAt(). So the matrix compute is pretty accurate
> based on the current device value.
> However in second method it seems to me that the transformation matrix
> is computed base on the current one multiple by the transformation matrix
> read from device. After a while numerically error will build up in
> the current transformation matrix. This may intensify in the long
> run so it appears that this rate is run differently from using
> the first method.
That's why I'm going to use the first method (now that I know what causes the
differences), even if
it is not as flexible as the second one.
But can you explain to me how you deal with the numerical error in your utility
classes like
MouseRotator ?
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".
