On Tue, 2009-12-01 at 09:14 +0000, Jussi Kukkonen wrote:
> Hi,
>
> This was something I've been meaning to ask, but keep forgetting: How am
> I supposed to use defaultPeer configuration item?
>
> This is what I'm trying (no non-default contexts or anything):
>
> 1. On UI startup: Call Server.GetConfig() onto get config value
> {"","defaultPeer"}. I assume using "default" as configuration/template
> name would work.
No. "default" is the name of a peer. If you don't have such a
configuration, the call with fail.
What you want is either "" (empty string) or "@default" (same thing,
spelled out explicitly) to select the default context in which peers are
configured. That way you get a config which contains all shared
properties, including "defaultPeer", without any of the peer-specific
properties.
> 2. When saving a configuration and setting it as default: Call
> Session.SetConfig() for configuration <name> with {"", "defaultPeer",
> "<name>"} in it.
I assume that "<name>" refers to an old-style config with no shared
properties. Use "" or "@default" when saving and it'll end up in
~/.config/default/config.ini, as expected.
--
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
