Revision history [back]
 | 1 | initial version | posted 2015-02-14 01:21:38 +0200 |
Add timezone setting when creating calendar event
This idea came to me when I was living with my time synchronization switched off (because Russian timezone changed and Jolla caught up with that a bit late). I switched off the time autosync, changed my timezone to a bogus one, and created several events in my calendar. Then when Vaarainjärvi fixed the Russian timezone I turned the time sync on again, and all my calendar events (made with the bogus timezone) moved by one hour. So I had to spend a lot of time double-checking if all my meeting schedules were correct.
Then there is another thing. I travel a lot, and I frequently need to create calendar events which will take place in another country. Example: I am in Russia, but I'll have a meeting in Switzerland in a week. Of course I know only the local (Swiss) time of the meeting. So I have to search the Swiss timezone on the Internet, calculate the difference, and create an event which is several hours 'later' so that the time becomes right when I actually come to Switzerland and my Jolla adjusts its timezone. This gets exponentially worse when daylight saving kicks in.
Yet another case: I frequently have to create a calendar event which should always take place at a certain time of day, e.g. in the evening, whatever country I'm in at that moment. There is no way I can do that now, no matter what calculations I perform.
Suggestion
- ALWAYS store calendar events' time in UTC - this way the events will never, ever "travel in time" on their own
- allow user to choose the event timezone when creating calendar event - this way the local time of the event will be always correct, even if the country's government issues a decree and changes the timezone
- add a "relative time" option, so that the event time is always the same in all timezones
| | 2 | retagged |
Add timezone setting when creating calendar event
This idea came to me when I was living with my time synchronization switched off (because Russian timezone changed and Jolla caught up with that a bit late). I switched off the time autosync, changed my timezone to a bogus one, and created several events in my calendar. Then when Vaarainjärvi fixed the Russian timezone I turned the time sync on again, and all my calendar events (made with the bogus timezone) moved by one hour. So I had to spend a lot of time double-checking if all my meeting schedules were correct.
Then there is another thing. I travel a lot, and I frequently need to create calendar events which will take place in another country. Example: I am in Russia, but I'll have a meeting in Switzerland in a week. Of course I know only the local (Swiss) time of the meeting. So I have to search the Swiss timezone on the Internet, calculate the difference, and create an event which is several hours 'later' so that the time becomes right when I actually come to Switzerland and my Jolla adjusts its timezone. This gets exponentially worse when daylight saving kicks in.
Yet another case: I frequently have to create a calendar event which should always take place at a certain time of day, e.g. in the evening, whatever country I'm in at that moment. There is no way I can do that now, no matter what calculations I perform.
Suggestion
- ALWAYS store calendar events' time in UTC - this way the events will never, ever "travel in time" on their own
- allow user to choose the event timezone when creating calendar event - this way the local time of the event will be always correct, even if the country's government issues a decree and changes the timezone
- add a "relative time" option, so that the event time is always the same in all timezones