|
From: Torsten D. <To...@t3...> - 2009-05-17 17:33:04
|
>>There is a bug in FGFCS.cpp that shows up after a reset of JSBSim in >>FlightGear. >>If you use a component hat has a name with an absolute path, the >>PropertyManager fails to tie this property to object methods after reset, >>because it is allready tied. > Torsten, were you referring to problems with component properties outside > /fdm/jsbsim/? IMHO you shouldn't place components outside /fdm/jsbsim/ - > use <output> if you need to affect properties outside /fdm/jsbsim/. Correct, the error occours only for properties outside the /fdm/jsbsim domain. (see my original post). I don't see any reason for not putting them into an arbitrary location in the property tree - until it's defined as illegal ;-) It currently does not work because of a "design flaw". I don't think it is a good idea to have two properties updated for the same purpose - the automatically created from the components name and one from the output element. And: <output> properties are not tied, so listeners do not get triggered on update. Jon, just to confirm, properties with relative paths do not produce the error message. Your memory still serves you well ;-) Oh - while typing this, I will try to name a component "../../some/name" instead of "/some/name" to check if this works... Torsten |