---- Reported by firstname.lastname@example.org 2010-04-07 00:10:22 +0000 ----
As discussed on the mailing list ("[SyncEvolution] auto sync"), it would be nice if D-Bus clients like sync-ui and also the command line (with --status) would be able to assure the user that automatic sync a) really is active and b) make it more obvious when it'll happen.
Jussi proposed the following API change:
> * GetAutosyncStatus() method that returns next estimated sync time
> and possible reason/status
> * AutosyncStatusChanged-signal that is fired when estimated time or
> reason/status changes.
Let's go for this. We need to define more aspects of it, though:
* must work also for "intelligent" auto sync (local or remote changes detected)
* must inform about all configs with auto sync, not just one
---- Additional Comments From email@example.com 2010-04-11 19:57:28 +0000 ----
patrick，I think this bug entry contains 3 problems according to your description:
1) notify clients about automatic sync
2) intelligent auto sync
3) sync ui shows more config info about auto sync
I'd like to open 2 other bugs to address the 2 and 3 items.
---- Additional Comments From firstname.lastname@example.org 2010-04-12 00:00:20 +0000 ----
(In reply to comment #1)
> patrick，I think this bug entry contains 3 problems according to your
> 1) notify clients about automatic sync
This is what this issue is about.
> 2) intelligent auto sync
> 3) sync ui shows more config info about auto sync
> I'd like to open 2 other bugs to address the 2 and 3 items.
Let's wait with opening new issues here until we have migrated the open feature requests from bugzilla.moblin.org. Perhaps there is already something about it, or we need to cross-reference with some of these issues.
--- Bug imported by email@example.com 2012-07-29 20:36 UTC ---
This bug was previously known as _bug_ 535 at https://bugs.meego.com/show_bug.cgi?id=535
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/SyncEvolution/syncevolution/issues/143.