For the sake of completeness, there is also the xml parameterization system
often used for panel/instrument configuations. However, the down side of
that is that it can lead to some crazy/convoluted path names that can be
brittle and are highly dependent on nesting levels -- a functional
but unwie
On 09/24/2012 09:41 AM, Stuart Buchanan wrote:
> I think that will result in
>
> /config/weight-and-balance/passenger1-kg[0] = 60
> /config/weight-and-balance/passenger1-kg[1] = 75
> /config/weight-and-balance/passenger2-kg = 60
> /config/weight-and-balance/passenger3-kg[0] = 60
> /config/weight-an
On Mon, Sep 24, 2012 at 7:49 AM, Erik Hofman wrote:
> As far as I know XML is processed in order of appearance, so this should
> do the trick:
>
>
>
>
>
>75
>80
>
>
>
>
I think that will result in
/config/weight-and-balance/passenger1-kg[0] = 60
/config/weigh
On 09/23/2012 06:28 PM, Curtis Olson wrote:
> I have a question about the Flightgear xml config system and doing
> "includes". This is an arbitrary example, but let's say I have an xml
> config file called "main.xml":
>
>
>
>
>
>
>
> The passenger.xml file might look like the follo
I have a question about the Flightgear xml config system and doing
"includes". This is an arbitrary example, but let's say I have an xml
config file called "main.xml":
The passenger.xml file might look like the following:
60
60
60
60
In the property tree after this loads
5 matches
Mail list logo
