On 30.10.2011 11:02, Durk Talsma wrote: > 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.
Durk, for me, it does still work. However, it's all a bit fragile. The are no error messages and any typo warps you to some random time. Also, we're using signed 32bit integers for the time offset - so things will break on 2038:01:19 ;-). I have a patch which cleans up the time/date option parser, adds proper checks and messages, also extends the time type to 64bit. Also makes it possible to use partial dates/times. "--start-time-gmt=2010" would only change the year then - but keep the current month/day/time. I could push that right away - but I'll delay that for later today, to not complicate your current hunt ;-). cheers, Thorsten ------------------------------------------------------------------------------ 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 Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
