-
• #27
Well, the time zone can be set in half-hour increments in the "Locale" settings, so that's already taken care of.
-
• #28
I would suggest adding to the language selection in the language app a selection for the timezone and saving the next few changeover dates together with the amount of change together with the locale stuff.
custom.html could use https://momentjs.com/downloads/moment-timezone-with-data-10-year-range.min.js .
Usage: moment.tz.names(); would give all timezone names to select from (or two step selection with moment.tz.countries() and moment.tz.zonesForCountry(String); ), moment.tz.zone(String) gives the zone data for a selected name.
Either upload this zone data directly or use the packed format: https://momentjs.com/downloads/moment-timezone-utils.js provides moment.tz.pack(UnpackedZoneData)
From https://github.com/moment/moment-timezone/blob/d7f687ea598b205806decd83b78d3ea9ad11a569/moment-timezone.js#L48 to https://github.com/moment/moment-timezone/blob/d7f687ea598b205806decd83b78d3ea9ad11a569/moment-timezone.js#L136 is the code needed on the Bangle.js to unpack data. -
• #29
Sounds good to me. The amount of extra data needed should be tiny as long as the language app pulled out only what was required.
-
• #31
Why not extend Settings with a html page like @DerGuteWolf suggested for locale?
Or more radical integrate Locale in Settings but still create the setting and the locale file on Bangle.
-
• #32
Sorry, old thread. But I guess this never happened?
-
• #33
same question that I asked myself this morning ...
-
• #34
Hi - no, I'm afraid it didn't - but the app loader should have detected that the time was wrong by more than a few minutes and updated when you next connected... Or maybe we don't include timezone in the time check?
yeah, timezone have a similar problem, ther are half an hour based timezones also...