David Megginson writes: > >The issue is code design -- Indeed !
>the view code needs to be fully decoupled It is except for the current_tilt current offset goal_view_offset goal_tilt_offset mechanisms. These are dynamical properties that should be stored in either a quat or a matrix and not as absolutes as they are now. As you appropriately say these valuse can be set by anything the keyboard mouse joystick whiplash due to plane_accelerations ect You just have to learn to trust the math and allow the Matrix/Quat manipulators todo the right thing ! They really do hold all the information necessary just as you discovered the 'convenient comment' in the Viewer code that allowed you to get the desired axis for your 'tilt' by inspection What the LinearAlgebra Team needs from the rest of the group is a concisely written requirements list for the Interface IAW step (1) of the extreme programing technique Regards Norman _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
