2 ms·
I do. One presumes that Microsoft, Apple and other major OS developers did exhaustive UX studies, and that this - "determine my location and set the timezone re
by FireBeyond 13y ago
I do. One presumes that Microsoft, Apple and other major OS developers did exhaustive UX studies, and that this - "determine my location and set the timezone representation of the clock to that local time, rather than the original" - wasn't something that a significant portion of people felt.
Why do I say this? There are very few use cases I can think of - though I'm happy to be educated otherwise - for doing this differently. In addition, Outlook and Calendar on my Mac both pick up TZ changes and automatically re-render my calendar appropriately.
I really struggle to picture a use case of "I fly from my home in Seattle back to Australia, and yet I want the clock on my menu bar to display a wall-time 18 hours behind my current location, rather than displaying the current time where my eyeballs are at, and changing back upon return".
Actually, I can think of one - the fear that poorly programmed or tested applications may handle this incorrectly. In which case I can understand this desire, even as a facet of "solving the wrong problem"/shooting the messenger.
- CamperBob2 13y agoOne presumes that Microsoft, Apple and other major OS developers did exhaustive UX studies, and that this - "determine my location and set the timezone representation of the clock to that local time, rather than the original" - wasn't something that a significant portion of people felt. Would these be the same studies that Microsoft cites to justify force-feeding Metro to desktop users?