Jim Wilson writes:
> Oops, yes it does, I've been doing a similar thing, althought
> haven't done anything with the animations. Can you send me what
> you've got and I'll try and merge with what I have?
I'll send you what I've got a little later this evening.
> Also: what I would like to do is setup a "/sim/model" property
> structure that has the pointers to the position and orientation
> data.
That's an interesting suggestion. I've been thinking about something
similar but with a little more information, perhaps something like
this:
<models>
<model>
<name>Aircraft</name>
<longitude-deg-property>/position/longitude-deg</longitude-deg-property>
<latitude-deg-property>/position/latitude-deg</latitude-deg-property>
<altitude-ft-property>/position/altitude-ft</altitude-ft-property>
<roll-deg-property>/position/roll-deg</roll-deg-property>
<pitch-deg-property>/position/pitch-deg</pitch-deg-property>
<heading-deg-property>/position/heading-deg</heading-deg-property>
</model>
</models>
With the refactoring I've done today, supporting something like this
is only a few lines of code away. This isn't a good solution for
objects in general, but as Andy mentioned, it will be useful for
adding the occasional aircraft carrier, etc.
I'm not going to do this now, though -- I'd like to stabilize my other
changes first.
All the best,
David
--
David Megginson
[EMAIL PROTECTED]
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
