---- Reported by rustonm2005@yahoo.co.uk 2010-04-21 03:47:50 +0000 ----

Using syncevolution-frontend 0.3

To Reproduce Issue:
1) Open the GUI application
2) Select the syncronisation service
3) Tick the "Automatic syncronise daily" box
4) Set a valid sync time (e.g. 07:00)
5) Go back to list of services
6) Re-select the same service (Sync time still set as 07:00)
7) Untick the "Automatic syncronise daily" box
8) Go back to list of services
9) Re-select the same service (Previous sync time is reset to current time)

Expected Result:
9) Previous sync time (e.g. 07:00) is remembered

Actual Result:
9) Previous sync time is reset to current time



---- Additional Comments From ovek@debian.org 2011-06-19 18:20:23 +0000 ----

Just going to update this report by saying that this behaviour isn't accidental - it was a part of the design from the start. The program's only knowledge of the sync time was meant to be the sync job itself, which is stored in the N900's alarm database. If you disable the job, then the alarm is removed and, with it, any knowledge of the previous sync time. To enable the job again, a new time has to be set, and the default happens to be the current system time.

It may be a valid issue, so I don't think I should close this bug, but I'm not likely to change this anytime soon. Unless, I suppose, someone makes a decent patch.



--- Bug imported by patrick.ohly@gmx.de 2012-08-19 20:56 UTC  ---

This bug was previously known as _bug_ 1133 at https://bugs.meego.com/show_bug.cgi?id=1133

Unknown platform unknown. Setting to default platform "".
Unknown operating system unknown. Setting to default OS "".