What's the best way to handle a long list in settings?

Hello,

What's the best way to handle a long list in settings?

I am making a watch face where the user can select a time zone or Zulu offset.  There are over 30 different time zones around the globe and I'd rather not do a super long list.  Mainly because I'd have to create over 30 items in the list, then re-create this in strings.  Any thoughts?

I've considered doing 5 different number entries (1st for plus or minus, 2nd & 3rd for hours, 4th and 5th for minutes), but I have no say in the formatting of the settings page (other than <group>) to make it look obvious.  

I tried asking for the hours separate from the minutes (constrained with min-max), but i don't think it was clear what I was looking for.

I could ask for the time zone as a string and then reference a database, but then I'd have to create and maintain a database of currently 117 time zones (https://www.worlddata.info/timezones/index.php).

Thoughts?

Top Replies

All Replies

  • Yes. AZ is in the Mountain timezone yet it observes different rules, thus it is a different timezone. Zen. Have a good day Jim. 

  • AZ IS in the Mountain Time Zone.  Most of the state just doesn't do DST.  Computers started using US/AZ a few years back, but it used to me Mountain Time, with a switch to use DST or not.  That's also the way it is with "Atomic clocks" that sync time based on WWV radio signals.  MT, no DST for me!

    Ask anyone that lives here what time zone we are in and they will tell you mountain time.

  • Next time tzmap gets sent out (probably this fall) look at the change log on GE, You'll see where dates change, some places opt out of DST, etc.

    The funny thing is you seem to understand that the tzmap ("time zone map") includes information about daylight saving time rules, but you deny that in Windows (for example) "Mountain Time" and "Arizona" are two different "time zones".

    Exempts states that don't do DST (AZ and Hawaii)

    Notice that Windows has separate entries in the "time zone list" for AZ and Hawaii.

    And as far as always DST in the US (I doubt that will happen)

    https://villagerpublishing.com/colorado-will-keep-daylight-saving-time-year-round-if/

    On June 2, Governor Jared Polis signed HB22-1297, Daylight Saving Time Year Round, into law, making Colorado the nineteenth state to have passed a law expressing a preference to stay on daylight saving time permanently.

    ...

    The new Colorado law also requires that at least four other states in the mountain standard time zone adopt permanent daylight saving time before our state does so. Utah, Wyoming and Montana have already passed laws stating they will make the change if Congress acts to permit it. New Mexico, southern Idaho or Arizona could be number four if they choose to act. 

    It sounds like they need one just more state to opt-in.

  • You act like a *** 5 year old child right now. Accept that you need to change your stance.

    ETA: the forum software censored by f word, but it should say copulating written differently.

  • AZ IS in the Mountain Time Zone.  Most of the state just doesn't do DST.  Computers started using US/AZ a few years back, but it used to me Mountain Time, with a switch to use DST or not.  That's also the way it is with "Atomic clocks" that sync time based on WWV radio signals.  MT, no DST for me!

    2 definitions of "time zone".

    Windows has separate entries in its "time zone list" for Hawaii and Arizona, so it's not using your definition (based on your own logic), it's using the "time zone + DST rule" definition.

    Other systems work in a similar fashion when asking you to "manually select a time zone".

  • Ask anyone that lives here what time zone we are in and they will tell you mountain time.

    That is the political/legal/social/human-friendly/geographical definition of time zone.

    The computer definition is different.

  • Accept that you need to change your stance.

    Jim is extremely knowledgeable and helpful, but when it comes to an argument where he's dug into an objectively wrong position he will never change his stance or admit that he's wrong. (A similar example is the bug where Garmin/CIQ incorrectly uses today's date to determine the DST logic to apply to a date in the past or future. According to him, what Garmin does isn't right or wrong, it's just a "matter of opinion.")

    This is the case even when everyone on all sides realizes the argument is mostly about semantics (except for the fact that the "time zone list" in Windows and other systems is clearly using a different definition of "time zone" than he is, because they contain distinct entries for "Arizona" and "Hawaii", for example.)

  • No, he is saying that the US/Mountain time (the science bit) is the timezone Arizona is in, and foregoes on the human factor. He is so hung up on that first bit that he misses the human factor.

  • No, he is saying that the US/Mountain time (the science bit) is the timezone Arizona is in, and foregoes on the human factor. He is so hung up on that first bit that he misses the human factor.

    IMO, he has a valid point that every non-technical person would say they are in the "Mountain Time Zone" if they live in Arizona. Even the wikipedia article for Mountain Time Zone says so (look at the map and the mentions of Arizona in the article text.)

    The argument of which definition is the "human definition" isn't super important here tho.

    The real argument is which definition should a Connect IQ app use, given that the user wishes to "manually select a time zone" and also wants the app to automatically adjust for DST? I would argue it should use the same definition as Windows, Steam Deck, several Linux distros, and many other systems.

    Some systems like smartphones and Macs just ask you to enter a nearby city (if the user turns off "automatically determine time zone"), but that's not feasible for CIQ. If only Garmin Connect settings supported a location picker, then you could pick a location, save the coords to settings, and use a LocalMoment in System 5.

  • Right, he/they are taking the stance that evolution deniers also take: It is just a theory and use the dictionary term of the word instead of the science definition of the word.

    We are in US/Mountain but we don't observe DST. Right, so you are in US/Arizona. No, we are in US/Mountain without DST. Right, US/Arizona is what you are refering to. I need to automate this bit to rinse repeat these last few sentences ad nauseam.

    I'm out, kthnxbye