I believe I have discovered a daylight saving time bug (connectiq 1.1.3). It seems that when you get the info for a moment in order to display this, it displays it with respect to the current daylight saving time rather than the appropriate daylight saving time for the moment.
Take the following code which creates a moment based on the values specified given in UTC:
var m = Greg.moment({ :year => 2015, :month => 10, :day => 15, :hour => 14, :minute => 0, :second => 0 });
var i = Greg.info(m, Time.FORMAT_MEDIUM);
Sys.println(Lang.format("$1$ $2$ $3$ $4$:$5$:$6$", [i.month, i.day, i.year, i.hour.format("%02d"), i.min.format("%02d"), i.sec.format("%02d")]));
m = Greg.moment({ :year => 2015, :month => 11, :day => 15, :hour => 14, :minute => 0, :second => 0 });
i = Greg.info(m, Time.FORMAT_MEDIUM);
Sys.println(Lang.format("$1$ $2$ $3$ $4$:$5$:$6$", [i.month, i.day, i.year, i.hour.format("%02d"), i.min.format("%02d"), i.sec.format("%02d")]));
This outputs:
Oct 15 2015 15:00:00
Nov 15 2015 15:00:00
The first line is correct. I am based in the UK, currently in daylight saving time until Oct 25th, so when I give a time of 14:00 this is correctly displayed as 15:00 in localtime.
But the second line is incorrect. By then we are no longer in daylight saving time, so the time displayed should be 14:00:00.
Further confirmation of this bug is that if you use the Garmin Sun & Moon widget, and page down to Oct 25th, the times should jump by an hour due to the change of daylight savings. But they do not. The times from Oct 25 onwards are (for me) an hour out. They appear to be displayed assuming daylight saving is still in operation, when it is not.
It appears as if the Gregorian.info is outputting the time based on the current daylight savings rather than the appropriate daylight savings for the date we are getting information for.
Is this a known bug? How should I be reporting bugs? Should I email [email][email protected][/email]?