On Tue, 2004-11-30 at 09:05 +0100, Ron wrote: > And here is a very small patch for one of the Xlib crashes. > apply this patch from the topdir of multisync like this: > > patch -p0 < <path to>/evolution_ecal.patch > > Standard disclaimers apply like "make a backup first" :) > > in the function evo2_calendar_modify when the passed variable data is > null the function tries to delete the entry with uid from evo and > returns TRUE if it succeeded. If it does not succeed the function goes > on and assumes there is valid information in data. This will of course > fail and make multisync fail. > > So if data is null and the deletion fails we should return FALSE to > signal failed deletion.
Thats absolutely true of course! Thanks for the patch :) > > Ron -- Armin Bauer <[EMAIL PROTECTED]> ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Multisync-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/multisync-users
