Hello Francesco,
Francesco Tamagni wrote:
> hi to all!
>
> playing with TrackballNavigator, i noticed a strange behaviour, i don't
> know if it is a bug or a feature, in any case it is not well documented.
>
> My issue: i was trying to set( Matrix ) on a TrackballNavigator, using a
> Matrix obtained using getMatrix() on another one. I did expect the
> viewing parameters of both navigators to be the same after set. I was
> wrong. The only way to achieve my goal is to use set( from, at, up )
> after getting from at up out of the source navigator.
>
> The reason is that set( Matrix ) does not copy the matrix directly, but
> infers (from at up) triplette from the given matrix, using the *old*
> _rDistance to calculate at point, and then internally re-creates the
> matrix using set( from, at, up ) using the just calculated parameters.
>
> If the old _rDistance is different from the one i expect to set using
> the new matrix, the result is different from the one i expect to obtain.
>
> If it is a feature, i suggest to add a line in the documentation to make
> it clearer, if it is a bug i hope this post is useful to solve the issue.
well, strictly speaking it is neither bug nor feature, the matrix just
does not carry all the information to recover from, at and up, but they
are needed by the Trackball navigator, so it kind of guesses that info.
But you are right, of course, this should be documented (I just added a
note to the function), thanks for pointing it out,
Carsten
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
