Default value of the TimeZone option

[balala]

Hi everybody,

Now it's my turn again to ask something. I have the following extremely simple Time measure:

Code: Select all

[MeasureTime]
Measure=Time
Format=%H:%M

If I add a TimeZone=0 option, I get the current UTC time. This does work.
If I add any valid numeric value to the TimeZone option (eg TimeZone=2 or TimeZone=-5) I get the appropriate time. With TimeZone=local I get the local time. All this are workign as well.
But if I add any (let's say) invalid string (for instance TimeZone=locale or TimeZone=Whatever), I get the time as for TimeZone=0, not my current local time. This seems a little bit intricating, because as far as I know if an invalid value has been used, the measure should use the default value, which in this case should be TimeZone=local.
Where is the mistake?

Thanks in advance.

[brax64]

Hi everybody,

Now it's my turn again to ask something. I have the following extremely simple Time measure:

Code: Select all

[MeasureTime]
Measure=Time
Format=%H:%M

If I add a TimeZone=0 option, I get the current UTC time. This does work.
If I add any valid numeric value to the TimeZone option (eg TimeZone=2 or TimeZone=-5) I get the appropriate time. With TimeZone=local I get the local time. All this are workign as well.
But if I add any (let's say) invalid string (for instance TimeZone=locale or TimeZone=Whatever), I get the time as for TimeZone=0, not my current local time. This seems a little bit intricating, because as far as I know if an invalid value has been used, the measure should use the default value, which in this case should be TimeZone=local.
Where is the mistake?

Thanks in advance.

Hi Balala,
I don't know the answer to your question, sorry... but to get the UTC time, I've to use TimeZone=-1, is that depending by the DST?

[balala]

Hi Balala,
I don't know the answer to your question, sorry... but to get the UTC time, I've to use TimeZone=-1, is that depending by the DST?

Yep, I suppose it does. However my question is related to what value is used for TimeZone if a non-valid string is set on.

[Mor3bane]

Yep, I suppose it does. However my question is related to what value is used for TimeZone if a non-valid string is set on.

Sorry if I am missing the point, but why would an invalid data string be required to work?

If its wrong then it should simply throw an error in the log, ya?

[CyberTheWorm]

Code: Select all

[MeasureTimeZone]
Measure=Time
Format=UTC

I just use UTC

[Alex88]

From what I've tried, once TimeZone= is present within the measure, having it blank or with or without a valid value, it seems to default to 0. Then when TimeZone= is not present, it defaults to the stated local time. I'm just guessing at the details of how it works, but that could mean if the TimeZone= option is present, it converts to looking for numerical values only aside from local, so 0 is the new default?

[jsmorley]

Code: Select all

[MeasureTimeZone]
Measure=Time
Format=UTC

I just use UTC

That is an error, which defaults to 0. It's a happy error, in that the result is what you want, but I don't particularly recommend it.

[CyberTheWorm]

That is an error, which defaults to 0. It's a happy error, in that the result is what you want, but I don't particularly recommend it.

OK dumb me, well at least UTC is TZ 0

[balala]

That is an error, which defaults to 0. It's a happy error, in that the result is what you want, but I don't particularly recommend it.

Alright, but the question is if a not-valid string is used why we don't get the result as for TimeZone=local (the default value), but as for TimeZone=0.

[Mor3bane]

I may have the logic wrong, but the local parameter is indeed the local time the computer uses, whilst 0 is the equivalent to the UTC timezone, as is whatever locations are at -4, and +9. Being numeric as the 0 to + or - 12 range are.