GNOME Bugzilla – Bug 522010
should not have to pick a city to pick a timezone
Last modified: 2020-11-06 20:19:33 UTC
This report has been filed here: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-panel/+bug/199644 "The layout of the current location selector suggests that you should pick a location name before picking a timezone. As mentioned in the somewhat related bug #522008, I don't care about the weather functionality, so I shouldn't have to come up with a location name (or select one from the finder) to configure a timezone setting. If you leave the location name blank and select a timezone, the location name is automatically configured for you, but there's no indication in the UI that this will happen. Likewise, if you use the location finder the timezone and lat/lon. will be populated for you, but a) only if your city is in the list, b) the finder window is so small by default that you have to scroll to see enough context to know you've picked the right city instead of another city of the same name, c) the location name populated by the finder is only the city name - whereas if you select the timezone first you get "<city>, <country>". If bug #522008 were resolved to allow disabling weather handling altogether, then the "add location" dialogue when that option is set could be reduced to a simple timezone selector, with the location name, latitude, and longitude all implicit. I think that would be a major UI improvement here." Thanks!,
*** Bug 522252 has been marked as a duplicate of this bug. ***
I would really like to see this happen. Just today, I got bit by a nasty workflow disruption where I needed to know the time in another timezone. Under GNOME 2.20, this was simple (at least for me): add a second clock, set its timezone to UTC, 24 hour format, and I could do the math in milliseconds (+5, -7, whatever, easy stuff). Leave it there for future reference (till whenever I get upset with my current panel layout and trash it to save some space). So today, I need to know the time in another timezone. I first have to remember where I am (is it -4 or -5 this time of year? ahh EDT, it's -4. Then I have to add in the offset using 12hr format after being used to going from a 24hr base. Another few milliseconds conversion.) All and all, a few seconds of time wasted so far, but more than enough to completely make me forget what I was thinking about beforehand... :/ Okay, so I see the way to do it now is to add a location to see the time in another timezone. Bit of a drawback that I now have to click the applet to see the second time. Great, that's okay, we can deal. Enter "Greenwich" (yeah, pretty close to UTC right?). Zilch. So I'm off to Google a location in Europe on UTC that's actually in the dialog. Ouch. If I hadn't already completely forgotten about what I was working on, I most certainly have now. Maybe this is me being dense about world locations and timezones, but it's a real disruption. (A separate, but nagging and related, issue: maybe this is just me being dense again, but how do I add a second panel clock on a different timezone with the new system? Should I be able to set the time format based on the location? Should I open another bug for this?)
*** Bug 532383 has been marked as a duplicate of this bug. ***
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years. If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-panel/-/issues/ Thank you for reporting this issue and we are sorry it could not be fixed.