On 22 May 2011, at 22:11, Martin Spott wrote: > Now, since the most recent version of the ground network files are > distributed via TerraSync, I'd propose to place the jetway files in the > same directories. This would indeed require your scripts to look into > the custom scenery directories as well - which would be the preferred > option, because, as already mentioned, I'd like to reduce the > dependency of Scenery from the Base Package. > > The preferred way of referencing custom scenery data would be to have > some sort of variable as a reference for all subsystems/routines which > would refer to these directories, but I have to admit that I'm not > entirely certain about the current state. I'd say this is something > worth checking before we proceed.
I talked to Ryan on IRC last night, and we discussed this. I've some local mods to commit+test that basically do exactly what is described above; they allow Nasal (or really, the loadxml command) to hook into my existing 'find a file for an airport, in the scenery locations' code we use for the other 'airport scenery data' files. I'll hopefully commit this tomorrow, then Ryan can test, and then hopefully jetways can live in the airport scenery data happily. James ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
