I had wondered at one point whether properties would make it very simple to hook up various FDM parameters with associated FlightGear-side panel objects -- also (I assumed) referenced via properties.
I suspect now that this has a not-so-simple answer, and it will be plain to see here that this is an area I am not at all familiar with.
If I was to create an FDM for a hypothetical aircraft (call it the X-100) powered by six turbojets, I would of course like to have a 3D model and a panel for it. I suspect that I could not simply code up the definition for the panel, and link up the "live" panel components with the associated JSBSim-side properties. Correct? Even if this was possible, it would then (I expect) preclude other FDMs from using the panel model, and this is bad. I haven't looked at the FGInterface code in a while, but I suspect that that is where the handoff occurs, from JSBSim-side properties to FlightGear-side properties. True?
If true, is this optimal? Does it provide for good a plug-and-play design approach? Is there a better way? Is there a FAQ? :-)
Jon
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
