Ampere K. Hardraade wrote: > Right now, if one wants to specify a new livery for some of the animation > files, he/she will have to do this: > > aircraft-set.xml > + main.xml > [ + livery1.xml > [ [ + animation1.xml > [ + livery2.xml > [ [ + animation2.xml > [ > [ + animation3.xml
Maybe I am overlooking what is involved but it seems strange to have a different animation file for each livery. Are you sure you cannot put the main animations in a file that can be included by every livery file ? -Fred > We can make it possible to do something like this instead: > > aircraft-set.xml > + main.xml > [ + livery.xml > [ [ + animation1.xml > [ [ + animation2.xml > [ > [ + animation3.xml > > Regards, > Ampere > > > On July 25, 2004 04:31 am, Erik Hofman wrote: > > Ampere K. Hardraade wrote: > > > No. What I want to do is tell each of these animation file where the > > > livery resides. I want to be able to tell all of them with in one single > > > file, instead of having to create a new xml file for every animation > > > file. > > > > Ah, That's what you meant. I don't think that multiple includes would > > solve this problem either. > > > > One solution might be putting the texture path into a property (and let > > the top-level model animation configuration file override the default) > > but that would mean that *every* model has to include a texture path... > > > > We would have to think a bit more about this. > > > > Erik > > > > _______________________________________________ > > Flightgear-devel mailing list > > [EMAIL PROTECTED] > > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > > _______________________________________________ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
