> . all day events: syncing between Evo and s55 of all-day events > results in midnight-midnight events in the s55. a) this is done in > GMT, so its 8am -> 8am for me, and b) midnight-midnight localtime > spills over into the next day (looks bad on s55 calendar, I saw > someone else asking about that too).
"All day events" are a big issues as each device seems to handle it its own way. > I patched the code to equate vCal v2 all day events to vCal v1 > zero-minute events at midnight on the day. Which is great for the > s55 (but probably not so good for other v1 vCal devices; Perhaps should these hooks be implemented on a device by device basis ? This would solve lot of side effects. This is IMHO the best solutions. Hub ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Multisync-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/multisync-devel
