View Single Post
Posts: 1,141 | Thanked: 781 times | Joined on Dec 2009 @ Magical Unicorn Land
#464
Originally Posted by nicolai View Post
That is really strange. I had so many bugs with wrong time offset, which
I got fixed only by using the TZ and TZ-offset.

I am afraid I can not simply remove this time offset from the timezone,
as in other cases the time offset may be wrong again.

Nicolai
(disclaimer: I didn't look at the code )

If you're using TZ/TZ-Offset of the event, I think that's the cause of the problems.

You can reproduce the error without MfE as well:

I set time zone to to America/Chicago. (GMT -5)
Create new event for 5:00
Cal-Home widget shows event at 5:00
Change time zone to America/New_York (GMT -4)
Cal-Home widget still shows event at 5:00, but it should be 6:00

(you can use any time zones as long as they differ)

The UTC timestamp in the calendar database is correct in every case.

I think using the TZ/TZ-Offset of the event is fundamentally the wrong thing to do. The event does not necessarily happen in the same TZ the N900 exists in. For example, if I live in New York and I get an meeting request from someone in Tokyo, I don't want to see Tokyo local time, I want to see New York time. Or if I am traveling, I want my times to reflect the time zone where I am presently located, not the time zone I was in when the calendar entry was created.

I think you should read time zone of the N900 and compute the offset from UTC start and end times based on that. TZ of the event itself is irrelevant. In my opinion.

Forgive me if I misunderstood or made false assumptions about how it is calculated. I'm only trying to help. Thanks.
 

The Following 2 Users Say Thank You to stlpaul For This Useful Post: