On Mo, 2010-11-08 at 08:58 -0300, Matías Parmigiani wrote:
I make a form where the users can select the different options for
peer I expect when the user press the make config file the application
generates the complete syncevolution config folder with the peer
inclusive for bluetooth connection. In fact the application creates
the config files in place fir the peer inside a model folder for each
one connected, but when I execute the command to make sync (with
another button in the app) just don't do it. I really suspect that ins
just a config problem, but I can't discover where is the error.
Have you compared it against a configuration created by the sync-ui
application? It is pretty obvious that your configuration is completely
broken, for example default/peers/nokia_6210/config.ini contains just a
single line with "defaultPeer = 6210".
I give you the config screen of the app(sync-options-Nokuntu.png),
syncevolution folder generated for my nokia 6210 navigator
(my_syncevolution_config.tar.gz) and the sync result in a file
Please, don't reimplement the configuration creation mechanism. Better
use the SyncEvolution D-Bus API for that. It'll avoid such mistakes as
the one above and will reduce the maintenance effort: the API is more
stable than the underlying file structure.
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.