Martin Spott wrote:
> Alez Buzin wrote:
>
>
>> May I have miss something but I have in FG properties
>> "sim/time/gmt" in the form "2009-05-16T12:08:16",
>> "sim/time/gmt-string" as "12:08:16",
>> and sub-trees sim/time/utc/... and sim/time/real/... containing year,
>> day etc as integers. What
Alez Buzin wrote:
> May I have miss something but I have in FG properties
> "sim/time/gmt" in the form "2009-05-16T12:08:16",
> "sim/time/gmt-string" as "12:08:16",
> and sub-trees sim/time/utc/... and sim/time/real/... containing year,
> day etc as integers. What problems to use this?
Working wi
Hi
May I have miss something but I have in FG properties
"sim/time/gmt" in the form "2009-05-16T12:08:16",
"sim/time/gmt-string" as "12:08:16",
and sub-trees sim/time/utc/... and sim/time/real/... containing year,
day etc as integers. What problems to use this?
With respect,
Alex
---
I think if you are recording absolute times of day it makes sense to store
those internally as unix time. I'm sure we could expose some sort of
function (if it's not already available) to format that in the local time
zone or some arbitrary time zone. I think this also facilitates computing
futur
On 9 Jun 2009, at 17:12, Erik Hofman wrote:
>> At the end of the day, the "correct" approach really depends on
>> what you
>> are trying accomplish (what values and in what format are you
>> trying to
>> compute?)
>
> Also, there is a difference between the value in the property tree
> (which
Curtis Olson wrote:
> Hi James,
> At the end of the day, the "correct" approach really depends on what you
> are trying accomplish (what values and in what format are you trying to
> compute?)
Also, there is a difference between the value in the property tree
(which is just a nifty way to loo
Hi James,
I know that unix time is used heavily internally in the code. I guess you
are right, I can't point to a place where it exists in the property tree
(which doesn't mean it might not be in there somewhere.) :-)
I don't see any problem with publishing the integer time in the property
tree
On 8 Jun 2009, at 23:12, Martin Spott wrote:
>> Actually the "official" FlightGear time matches the unix approach of
>> tracking seconds since the epoch.
>
> Well, the scope on which James is focusing in his question is -
> obviously - the property tree and so far I've been unable to spot a
> pla
Curtis Olson wrote:
> On Mon, Jun 8, 2009 at 2:04 PM, Martin Spott wrote:
>> James Turner wrote:
>>
>> > Is there an accepted way to store an absolute time (as opposed to an
>> > interval or delta) in the property tree? [...]
>> FlightGear's "official" time seems to be seconds since midnight
On Mon, Jun 8, 2009 at 2:04 PM, Martin Spott wrote:
> Hi James,
>
> James Turner wrote:
>
> > Is there an accepted way to store an absolute time (as opposed to an
> > interval or delta) in the property tree? The obvious way (to me)
> > would seem to be using a double to store seconds since the Un
Hi James,
James Turner wrote:
> Is there an accepted way to store an absolute time (as opposed to an
> interval or delta) in the property tree? The obvious way (to me)
> would seem to be using a double to store seconds since the Unix epoch,
> but it's not exactly human-readable. Of course
Another of those simple-but-awkward questions:
Is there an accepted way to store an absolute time (as opposed to an
interval or delta) in the property tree? The obvious way (to me)
would seem to be using a double to store seconds since the Unix epoch,
but it's not exactly human-readable. Of
12 matches
Mail list logo
