[Evolution-hackers] Creating iCal components

2006-08-01 Thread Teresa Thomas
Hi I have a question regarding libical. Since you authored the documentation, I figured you would know!Suppose my iCal string contains multiple events ie, looks as follows:BEGIN:VCALENDAR...BEGIN:VEVENT
...END:VEVENTBEGIN:VEVENT...END:VEVENTEND:VCALENDARI'm using the icalcomponent*icalcomponent_new_from_string(char*str) function to parse it. According to the libical documentation If the string contains multiple components, the multiple components
will be returned as the children of an ICAL_XROOT_COMPONENT component.What functions can I use to access these children vevent components? Code snippets would be great.Thanks!Regards,Teresa

___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers


Re: [Evolution-hackers] Creating iCal components

2006-08-01 Thread Teresa Thomas
Whoops! The above mail was supposed to be for the author of libical docs. But if anyone here knows the answer, then great! :)On 8/1/06, Teresa Thomas 
[EMAIL PROTECTED] wrote:Hi 
I have a question regarding libical. Since you authored the documentation, I figured you would know!Suppose my iCal string contains multiple events ie, looks as follows:BEGIN:VCALENDAR...BEGIN:VEVENT
...END:VEVENTBEGIN:VEVENT...END:VEVENTEND:VCALENDARI'm using the icalcomponent*icalcomponent_new_from_string(char*str) function to parse it. According to the libical documentation If the string contains multiple components, the multiple components
will be returned as the children of an ICAL_XROOT_COMPONENT component.What functions can I use to access these children vevent components? Code snippets would be great.Thanks!Regards,
Teresa



___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers


[Evolution-hackers] Bug in evolution with recurring event exceptions?

2006-08-01 Thread Scott Herscher
I cannot get Evolution to correctly display recurring event exceptions.  At 
this point, I'd ordinarily think that it's a bug in Evolution, however 
Evolution correctly display recurring event exceptions using the built-in file 
backend.  I've taken the bits of code out of the file backend that I thought 
were applicable and grafted them into my backend but still no love.  Anyone 
have any thoughts?

Scott
___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers