Jim Wilson writes:
> The mouse code should just output an RPH
>vector similar to what the "pilot offset" code does.
The problem is IMHO the other way around the External
View code should be exporting a matrix instead of a vector
Which is exactly what the Mouse Code did except for the
vestigial offset angle that the Mouse determines this Matrix
by using a Quat is completely inconsequential
Again what IMHO and I think most other peoples minds needs to
be done is a reevaluation of the whole 'Camera' Concept
Things that haven't been discussed recently but I am sure will be
brought up again are
1) I want to walk around the airplane and do my 'pre flight checks'
both in First Person and in External view mode
2) I want to switch from the X15 pilots 'eye' to the 'mother plane
pilots'eye'
not only when we are attached prior to but also during and agter launch
3)... a host of other possibilities
So I say lets take a little time and discuss or 'High Level'
conceptualization
and the possible ramifications of the possible way of doing things before we
just tear things apart just to fix the 'current crisis'
Object derivation can help a LOT here, something we are not doing
anywhwere near enough of. ie we are stuffing to much in the TopLevel
Class makeing nigh impossible at times to have alternative ways of
doing things
FWIW IMHO and I am sure is no surprise to anyone the worse offender
in this regard is the fgProperties module which should be derived from
a pure virtual class !!
Cheers
Norman
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
