erik wrote in Sat Dec 19, 2015 10:35 am:Which made me look into replacing tied properties with propertyObjects (once I was made aware of them) in JSBSim. It should be doable, but the inclusion of boost in the new properties code was a setback. Adding boost as a dependency for JSBSim standalone would be ridiculous.
I haven't looked at the code in a while, but as far I remember, there's nothing in it that cannot be worked around using the STL - boost was a controversial addition anyway (see Tim's and Mathias' comments in the archives).
Concerning JSBSim and tied properties in particular, you may want to look up Jon's and James' comments, summarized at:
http://wiki.flightgear.org/Howto:Use_Pr ... cts#JSBSimThat said, HLA is an active area of development, so it would make sense to encapsulate the property tree functionality anyway, even if just to prepare the interface for supporting multiple independent FDM instances, as per:
Subject: how can I control two aircraft?Torsten wrote:Currently, there is exactly one FDM controlling exactly one aircraft model in one session of FlightGear.
We have a very clever guy working on integrating HLA into FlightGear. Once that is implemented, the idea is already there to be able to virtually walk along a number of parked aircraft on the apron, click on any of them, enter the cockpit and go for a flight. But that's definitely still a long way to go.
Torsten
(Note that this would also nicely map to the idea of having "remote properties" in FlightGear:
http://wiki.flightgear.org/Remote_Properties )