Hi James, > > While I recently touched the options.cxx code, I would be 'surprised' if > that's broken the options above, given that other single-value options work. > (It's just passing a string through, and the functions that process the args > are unchanged) What's more likely, is that some of my refactorings in the > TimeManager code would have upset it, *except* that I made all those changes > pre 2.4, as far as I can recall - and certainly more than three months ago. >
I managed to narrow the problem down to a commit that occurred between October 12 and October 16. More specifically, FlightGear next: 3d544fb SimGear next: e4e31be still works, while FlightGear next : 0f5d27c SimGear next : bcf7ed5 is broken. I'll try to narrow it down, a little further, but it looks like this does involve your commandline refactoring work. If you happen to have any idea, please feel free. In the mean time, I'll try to find the exact commit that causes it. Cheers, Durk ------------------------------------------------------------------------------ Get your Android app more play: Bring it to the BlackBerry PlayBook in minutes. BlackBerry App World™ now supports Android™ Apps for the BlackBerry® PlayBook™. Discover just how easy and simple it is! http://p.sf.net/sfu/android-dev2dev _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
