> On Friday 30 March 2018 09:08:54 D. R. Evans wrote: >> I'm not sure where to report this: >> >> I have three 24-hour TDE clocks in a panel: one on local time; one on >> London time; and one on UTC. The London and UTC clocks are reading the same >> time, but I discovered yesterday that in fact London is already on summer >> time (and has been for nearly a week, I understand), so the London time >> should be displaying a number one hour higher than UTC. >> I have more info on this now, but still don't know where best to report it. The additional info is that logging out and logging back in -- which is something I rarely do; I often go weeks without doing so, but I happened to do it today -- "fixed" the problem. So what appears to happen (this is a guess, but it fits the evidence) is that the clock figures out the time in London at log-in time, and then starts free-running, keeping the same offset between the displayed time and UTC, regardless of subsequent changes to/from summer time that might occur during the logged-in session. In any case, the fact that the clock is unreliable and can display an incorrect time is obviously a bug, and I would hope that someone can look into the issue. (FWIW, the local clock -- Denver -- quite happily adjusted the time automatically and correctly earlier in the month.) Doc -- Web: http://enginehousebooks.com/drevans
Attachment:
signature.asc
Description: OpenPGP digital signature
