On 30.10.2011 12:49, Durk Talsma wrote: > Thanks for mentioning this. Your mail had more diagnostic value than > you perhaps realized.
Good. As often, any info may help... ;-) >> time. Also, we're using signed 32bit integers for the time offset - >> so things will break on 2038:01:19 ;-). > Hmm, yeah that's not good. Do you think that switching to time_t > would suffice for the "millennium bug"? Indeed, that was the classic "Y2K38 Unix millennium bug". ;-) We also needed to replace some fgSetInt by fgSetLong etc to get proper 64bit support. Seems all good now - at least for the next couple of million years... >> 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. > > Okay, that sounds good. Would your patch also be able to only set the > month, day (etc), without touching the other values? Good idea. Didn't work before you mentioned it - but was easy to change. So, you can now use something like --start-time-gmt=2011 --start-time-gmt=2011:12 but also --start-time-gmt=:::12:59:00 or --start-time-gmt=2038::3:12 Not all combinations seem useful, but it's flexible now. Any missing field remain unchanged. Admittedly, currently it's only fully correct when specifying start time in GMT. With system or local aircraft time hours may be a little off when the given time is incomplete. We need to extend sgtime to provide more conversion methods. >> I could push that right away - but I'll delay that for later today, >> to not complicate your current hunt ;-). >> > If this only touches the function that computes the date itself, I'd > say go for it. My tentative conclusion is that it's not the time > parsing function itself that's causing problems, but a conflict > between multiple command line options. But, maybe we should give > James a chance to have a look before complicating matters further. It's pushed now... Your issue sounds like something about the init sequence of command-line vs .fgfsrc config options has changed. James will probably spot that quickly... :) 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
