David Megginson wrote: > Andy Ross writes: > > Apropos of this stuff, David, you might want to look at panel.cxx > > and investigate parameterizing the panel location. > > I'd be thrilled for someone to take over the 2D panel code. I think > that the future lies with the 3D cockpit, and I'm thinking of ways to > carry most of the current panel work over -- we should be able to keep > the current instrument XML files (which represent 99% of the work > invested) and project each instrument individually into 3D space.
That's exactly the idea. You take a "plane of instruments" (what we're currently calling a panel XML file) and project it into 3D space via specifying corners. It draws on top of the existing stuff, with no problems whatsoever. If you want to have only one instrument per panel, that works fine. Most (well, all) cockpits, though, have a bunch of flat boards with instruments mounted on them. Call each one of those a "panel" and we're done. All the work carries over automatically. The only code changes required are to allow the corner vertices to be specified in the configuration (/sim/panels[n]/bottom-left/x-m, etc...), and allow more than one panel to be created at once. Maybe there's a need for a "cockpit" xml file to unify some of this. Andy -- Andrew J. Ross NextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com "Men go crazy in conflagrations. They only get better one by one." - Sting (misquoted) _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
