On Tue, 2014-10-28 at 23:23 +0000, Graham Cobb wrote: > My thought is to force the event to not be treated as an "all day" event > if the time fails the midnight check. Not perfect, of course (it loses > the information that it is an all day event), but it allows the user to > get a better idea of what has gone wrong and gives them a better chance > of recognising the correct day. Of course, it is likely to really mess > up round-trip processing of the events -- they may get marked by > Exchange as no longer all-day when they get synced back. > > Thoughts?
What you propose seems like the best (okay, least evil) approach. Is this something that you want to work on soonish? I'm thinking about tagging and releasing an updated of SyncEvolution (either 1.4.99.5 or 1.5) and could include an updated activesyncd. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
