On Saturday 01 July 2006 13:21, Durk Talsma wrote:
> Considering that this function is called Init, I believe that the statement
> on line 1413 is wrong. An init function should not carry over existing
> values or the very variable it is supposed to initialize. Therefore, I'm
> inclined to remove t
If my memory of the flightgear development history serves me correctly, we
originally used system time, without any option to change that.
This had obvious disadvantages, because it didn't allow any flexibility,
although I believe we already had the ("T"/"t") keyboard combinations to
advance /
I forget who setup the original --time-match-local options (and friends)
and I never really understood how they went together. I think if you do
test out a change here, make sure that the
--timeofday=dawn,noon,morning,night,etc. option still works correctly.
Regards,
Curt.
Durk Talsma wrote
Hi all,
I'm investigating a time-offset initialization problem, related to a broken
--time-match-local command line option. This option should set the local
simulator time to the same time as where I am in real life. For example, I am
located in a CET timezone, where it is 13:15, and want to fl
4 matches
Mail list logo
