Hi, do i assume correctly that you made an appointment with an reminder and entered "Appointment with alarm" as the message to display, correct?
The problem here is that the palm does not support this description correctly and therefor it will be lost when it is synced back. Multisync currently does not know anything about "Capabilities" of devices, it is a design limitation. your fix should not break anything therefor i will include it. thanks! Armin On Sun, 2004-01-04 at 20:29, Thomas Stieler wrote: > Hello, > > I have some problems performing a syncronization with Evolution (Version > 1.4.5) and a palm (Tungsten E). > > For an appointment with an alarm, evolution sets the property > DESCRIPTION of the VALARM component within the VEVENT with the value of > the SUMMARY property of the parent VEVENT component: > > Example (from file ~/evolution/local/Calendar/calendar.ics): > ----------------- > BEGIN:VEVENT > VERSION:2.0 > SUMMARY:Appointment with alarm > DTSTART;VALUE=DATE-TIME:20040104T180000 > DTEND;VALUE=DATE-TIME:20040104T190000 > UID:[EMAIL PROTECTED] > DTSTAMP:20040104T171943Z > LAST-MODIFIED:20040104T173204Z > CLASS:PUBLIC > TRANSP:OPAQUE > SEQUENCE:3 > BEGIN:VALARM > ACTION:DISPLAY > TRIGGER;VALUE=DURATION;RELATED=START:-PT15M > X-EVOLUTION-ALARM-UID:[EMAIL PROTECTED] > DESCRIPTION:Appointment with alarm > END:VALARM > END:VEVENT > > The palm plugin does not generate this property, so resyncing will lead > into a conflict: > > >From Evolution: | From palm: > ------------------------------------------------------------------------- > Summary: Appointment with alarm | Summary: Appointment with alarm > Starts: Sun Jan 4 18:00:00 2004 | Starts: Sun Jan 4 18:00:00 2004 > Ends: Sun Jan 4 20:00:00 2004 | Ends: Sun Jan 4 20:00:00 2004 > Description: Appointment with alarm > > > Whats about adding the property in the VALARM component? > > This patch in method calendar2vevent works for me, but I don't know if > there are adverse effects: > > [EMAIL PROTECTED]:~/pim/multisync/plugins/palm_sync> diff -u -w src/vcard.c~ > src/vcard.c > --- src/vcard.c 2004-01-04 20:20:47.000000000 +0100 > +++ src/vcard.c~ 2003-11-29 15:14:43.000000000 +0100 > @@ -145,6 +145,9 @@ > break; > } > > + if (appointment.description) > + addPropValueO(prop, VCDescriptionPropO, > appointment.description); > + > prop = addPropValueO(prop, VCTriggerPropO, buffer); > addPropValueO(prop, VCRelatedPropO, "START"); > addPropValueO(prop, VCValuePropO, "DURATION"); > > > > Regards, > Thomas ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Multisync-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/multisync-devel
