On Thu, 2005-07-28 at 17:38 +0200, Armin Bauer wrote: > > I'm a developer so i might be able to do some debugging if > > i knew where to start. Any ideas? > > > > ok to fix this bug we first have to find it :) > > so we need to know what exactly evo2 passes in to multisync and what > leaves multisync to opie. so a few debugging printfs might be necessary.
Ok, i'll look at the source code and see if i can print anything sensible out. > the other possiblity would be to port the opie plugin to opensync (see > www.opensync.org). opensync is the successor to multisync and has _much_ > better debugging capabilities. Opensync looks really promising but as i don't have any experience on syncing stuff i'll just try to fix evo/opie plugin and maybe port them later. -- -- Ville Ranki oh3gbq [EMAIL PROTECTED] 040-757 2533 http://www.vip.fi/~cosmo/ ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Multisync-devel mailing list Multisync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/multisync-devel
