paulw wrote:Indeed, I was a bit vague on that point. I live in Maryland (EST) but was home for the holidays in Utah (MST), so the event times are correctly stored at EST.
Based on what you're describing, it sounds like you had set the computer to MST when you performed the import. That would cause the behavior you observed.
I know that Google products (Gmail, calendar, etc.) all work this way. I first discovered it in Gmail when I was connected with Remote Desktop to a computer three hours away and all of the times were off on my email. It really threw me for a loop until I realized what was happening.
You could argue that this is both a bug and a feature. There isn't an easy answer, but most modern devices translate times based on the user's time zone. My Android phone changed time zones when we were in Utah over the holidays. That meant that I had to enter an appointment in MST when I entered it so that it would show up correctly when I got home to PST. It can be a hassle, but it becomes "normal" and corresponds with the way that most systems (cell phones, Google mail/calendar, Microsoft Outlook, etc.) work.
Although there might be advantages to having the ward calendar fixed to the ward's time zone, it's still going to get translated when a user syncs it to a Gmail account that syncs to an Android device (or some other arrangement of similar technology). I think that the consistency of behavior between devices and systems is more valuable than creating a system that is "buggy" for everyone who has learned to adapt to other systems in order to solve a problem for a subset of users.
Random related thoughts:
This is part of the reason that I don't change the clock on my computer when traveling. It's easier to know that the computer still thinks it's at home and I don't have to worry about weird time things, although I occasionally have to translate time zones in my head.
If you've got family in Arizona, you probably learned to deal with this at some point since Arizona doesn't observe daylight saving time.
We drove through northern Montana and Idaho recently and there are houses within a mile of each other in two different time zones (Mountain/Pacific). It created some interesting conversation when my children realized how those homes were affected. Perhaps they're better equipped to suggest how this should be handled. There are probably a few church units that span time zones and deal with this regularly.
And finally, I used to use a compiler that was time-stamped based on the compiler version. (2.1.08 was time-stamped 21:08, 2.1.10 was time-stamped 21:10) If you needed to know which version of the compiler was installed, you could check the timestamp on the compiler executable. The timestamp would occasionally get off by an hour for users on Windows NT systems because of the way it dealt with DST internally.