[Syncevolution-issues] [Bug 2764] Calendar event alarm synchronization between N900 and Goosync
http://bugs.meego.com/show_bug.cgi?id=2764
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|Undecided |Medium
Status|NEEDINFO |ASSIGNED
Target Milestone|--- |1.1
--- Comment #7 from pohly <patrick.ohly(a)intel.com> 2010-06-09 23:45:58 PDT ---
(In reply to comment #6)
GooSync writes:
Stuart, Jun 09 16:30 (BST):
Hi,
The N900 events were sent to us with invalid alarm times (as stated in the
replies to your bug report). These alarm times end up being set after the start
time of the event.
This is not quite correct. Given the right time zone as reference (the device's
local time zone), the alarm time is before the start time of the event. I don't
know whether GooSync allows setting a time zone for a device. Anyway, this
problem can be worked around as we did for other peers before: convert to
absolute start times.
But the mechanisms for doing it should be different: if alarm time is in local
time zone and start time is in UTC, convert to UTC, without checking what our
peer is (as we do wit relative alarm times).
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.