Hello! Another clarification...
commit 439f27574a0b2bc97074141959a0569e943d689c Author: Patrick Ohly <[email protected]> Date: Mon Sep 14 22:31:33 2009 +0200 D-Bus API: added clarification for temporary config changes It's debateable whether temporary config changes should affect future GetConfig or SetConfig calls. Let's keep it simple and define that they don't, which is in line with the original motivation of using them only for syncs. Once we add status queries, they might also be applied to those. diff --git a/src/dbus/interfaces/syncevo-session-full.xml b/src/dbus/interfaces/syncevo-session-full.xml index 9e8445d..f7ec758 100644 --- a/src/dbus/interfaces/syncevo-session-full.xml +++ b/src/dbus/interfaces/syncevo-session-full.xml @@ -33,7 +33,8 @@ <doc:doc><doc:summary>TRUE if configuration changes should only be used for the duration of the This is useful to run a single sync session with different settings, for example with an increased logging level. "update=FALSE" and - "temporary=TRUE" are mutually exclusive. + "temporary=TRUE" are mutually exclusive. Temporary config changes + do not affect getting or setting permanent configurations. </doc:summary></doc:doc> </arg> <arg type="a{sa{ss}}" name="configuration" direction="in"> -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
