I know people have mentioned various DST bugs, but as far as I've seen, nobody has produced a simple test case and shown the result (a simple watch face that shows the time and the dst and timeZoneOffset fields should be sufficient) and then a screenshot that shows the wrong result in action.
I could definitely write it up, but I don't have any free time right now..
I know people have mentioned various DST bugs, but as far as I've seen, nobody has produced a simple test case and shown the result (a simple watch face that shows the time and the dst and timeZoneOffset fields should be sufficient) and then a screenshot that shows the wrong result in action.
I could definitely write it up, but I don't have any free time right now..
Travis
Here it is: you can find screenshot from emulator, same code running on fenix3HR and a final screnshoot of GPS coordinates : place near Paris, Daylight saving is on.
The 2 numbers are timzoneoffset (3600 when no daylight saving, 7200 since end of march).
Here it is: you can find screenshot from emulator, same code running on fenix3HR and a final screnshoot of GPS coordinates : place near Paris, Daylight saving is on.
The 2 numbers are timzoneoffset (3600 when no daylight saving, 7200 since end of march).
And yes, timezones are updated.
sorry, second number is dst (3600 on emu, 0 on watch).
Be sure to use the format described in the sticky post at the top of the forum, and include code (you can email it to garmin if you don't want to post it in public)
Stepping back a bit, what do you want to do? Just see if you're in DST at your current location? With DST, even if you are in DST, that doesn't mean that it's DST in other places, as DST varies by country or even a specific region (I live in the US which does DST -at a different time than Europe- but live in a state that doesn't ever do DST, so half the year, New York is a 2hr difference, and the other half, 3hrs)
