Thanks for your patch. I have applied it to the CDE 2.2.1 source, rebuilt and reinstalled. It is indeed fixing the problem with the date at which DST starts in dtcm since the event scheduled at 2pm (1pm UTC) is shifted to 1pm after March 30 instead of March 9. However, the shift now has the wrong sign:
If I enter a recurring event at 2pm now that the legal time in Paris is UTC+1, it will be stored in UTC time in the calendar as a recurring event at 1pm UTC. After March 30, Daylight Saving Time is in place and the legal time becomes UTC+2. dtcm reads in the calendar recurring event at 1pm and should be showing it at 1+2=3pm. Instead, the event appears at 1pm (as if the legal time had become UTC). I had noticed one thing before applying the patch and rebuilding: using dtcm_lookup to print all the events taking place during March 2014 gave correctly the change of legal time on March 30. So the function used in dtcm_lookup to print the calendar entries did not have the bug. Now both dtcm and dtcm_lookup are giving consistent results for time of appointments. Best, E. Orignac On 03/11/2014 02:01 AM, Jon Trulson wrote: > On Mon, 10 Mar 2014, Edmond Orignac wrote: > >> >> As I explained in my previous message, dtcm has switched to Daylight >> Saving Time (UTC+2) yesterday (as expected for North America) although >> in the European Union the switch to Daylight Saving Time is scheduled >> for March 30. >> ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ cdesktopenv-devel mailing list cdesktopenv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
