http://bugzilla.moblin.org/show_bug.cgi?id=8059
--- Comment #7 from pohly <[email protected]> 2009-11-22 23:31:46 PST --- (In reply to comment #5) > > Because of this disadvantage I prefer a solution where per-peer views only > > remove the peer properties and non-peer properties have to be removed > > explicitly via a non-peer view. > SetConfig(False, {}) with config name '@default' is used to clear all peers? That removes everything in that context: shared sync properties, sources, peers. Global properties (eh, property: defaultPeer) and other contexts are left untouched. > I have a question for SyncConfig::remove. Suppose we remove a peer. we'll > invoke 'makeVolatile' to reset all nodes including global, context, etc. But > what if we need them again? we'll re-load them again? Yes. This particular SyncConfig becomes unusable, but because it is invoked on a temporary instance in the D-Bus Session, that is okay. (In reply to comment #6) > For global, context nodes, are they shared and stored in a specific place? Yes: ~/.config/syncevolution/config.ini - global default/config.ini - shared sync props -- Configure bugmail: http://bugzilla.moblin.org/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. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
