On 20 Jan 2011, at 23:47, Jacob Burbach wrote: > Ok, that does raise another question then. In order for the 'wrong' > method to work in any fashion, means you have to be recursively > searching the path given by --fg-aircraft...right? Seems odd, and > certainly serves to create ambiguity and confusion....so why are we > doing that? Would it not be much simpler to only search the top level > directories located under the path given with --fg-aircraft for the > set.xml or model.xml in question? Then you either give it the right > path and it works, or you don't, and it doesn't.
Actually the search has *always* been recursive - for years, by the look of it. I use the same (refactored) code to support all aircraft dirs, both the default one in fg-data, and the additional ones. Obviously I didn't want to break the existing support for the recursive search, so I kept it - so it works for all aircraft dirs. You're absolutely correct that it creates some ambiguity and confusion (and makes the code a little bit more complex). If that cost is judged to exceed that of removing an existing feature that *probably* nobody is using, I can remove it - the problem is sometimes when I do that, we discover much later that someone did actually want/like/need the feature :) James ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
