David Megginson writes:
Tony Peden writes:
/sim/startup/init/position-type : (latlon|airport|navaid|runway)
/sim/startup/init/altitude-type : (msl|agl|glidepath)
/sim/startup/init/orientation-type : (rph|runway)
/sim/startup/init/time-type : (utc|local|sunpos)
Norman Vine writes:
Not really -- the difference is that the actual values
(lat/lon/alt/hpr/airport/navaid/etc.) live in the main property tree,
and these tell us only where we should look for them.
Sounds to me like what is needed is a way to do
$MY_TREE = which branch I want
David Megginson writes:
Norman Vine writes:
Not really -- the difference is that the actual values
(lat/lon/alt/hpr/airport/navaid/etc.) live in the main property tree,
and these tell us only where we should look for them.
Sounds to me like what is needed is a way to do
David,
I'm open to something more sensible, but let's proceed with caution.
I have a side project that is critically wired into the current
presets arrangement and I can't afford to have that broken, at least
not for very long. Hopefully if you do make changes you are willing
to work with me to
Curtis L. Olson wrote:
David,
I'm open to something more sensible, but let's proceed with caution.
I have a side project that is critically wired into the current
presets arrangement and I can't afford to have that broken, at least
not for very long. Hopefully if you do make changes you are
On Fri, 2003-09-19 at 13:00, David Megginson wrote:
Unfortunately, while the presets hierarchy brought some benefits, it
also broke saving and restoring flights. I think that it's time to
consider doing away with the presets hierarchy, and trying something
like this:
1. Make an in-memory
Tony Peden writes:
/sim/startup/init/position-type : (latlon|airport|navaid|runway)
/sim/startup/init/altitude-type : (msl|agl|glidepath)
/sim/startup/init/orientation-type : (rph|runway)
/sim/startup/init/time-type : (utc|local|sunpos)
This sounds awful close to
