I know you guys don't expect anything less from me, so here's some odd
corner-case bugs. :)

With the CVS HEAD snapshot from last night: say you re-compile multisync,
and you forget to compile/install a plugin that you have configured to
be used by one of your sync pairs:

       - If *all* of them are missing, multisync dumps core.

       - Above *might* be true if just more that one plugin is missing,
         but I tested the all are missing case. Ahem. :P

       - If at least one plugin is missing, File/Quit just says "One
         or more plugins not found" and doesn't let you quit.


All of that being done, I started from scratch again.

For the first time last night I synced:

    Evolution <-> Backup
    Evolution <-> Opie (ftp over wifi)
    Evolution <-> t68i (bluetooth)

and damn if everything didn't just work.  I of course had to weed out
duplicate entries -- some of the same contacts were in Opie and on the
phone.  More advanced collision detection might be nice for around
1.0. :)

So is there a recommended "common" plugin to use (like I use Evolution
above)? Or does it matter?  If I want to sync to the t68i using BT
some times and IRDA other times, should I just re-configure the
sync-pair, or should I make one for each?

You guys rock.

-- 
Stephen L. Ulmer                              [EMAIL PROTECTED]
Senior Systems Programmer                         http://www.ulmer.org/
Computing and Network Services                      VOX: (352) 392-2061
University of Florida                               FAX: (352) 392-9440



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Multisync-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/multisync-devel

Reply via email to