Trixology
WeatherCat => WeatherCat General Discussion => Topic started by: Alan Rowley on November 18, 2015, 08:40:24 AM
-
Hi all,
On my monthly climatological summary page, the timings of the various events is +1 hour. I hadn't noticed this before, but I know last night's high wind speed was at 22:30, but the summary is showing 23:30. I know it was 22:30 because I was outside checking the damage it did to my roof.
What do I need to do to correct this - the timings, not the roof?
Monthly climatological summary (http://www.brackenhouse.net/weathercat/uploads/thislastmonth.shtml)
Thanks - ALAN.
-
Alan, I hope this doesn't mean the DST gremlin is still a part of WeatherCat 2. It appeared to have been squashed for my needs:
http://athena.trixology.com/index.php?topic=1901.0
-
The 1 hour offset certainly sounds like a DST issue - it'd be interesting to see if it corrects itself at the end of the month.
I'll raise a bug for it, thanks for the report [tup]
-
The 1 hour offset certainly sounds like a DST issue - it'd be interesting to see if it corrects itself at the end of the month.
I'll raise a bug for it, thanks for the report [tup]
Ouch, that's starting to sound like the DST bug might not be totally solved after all. Please consider rolling this into the previous bug. I'd hate to think Alan would have to wait two years for this report to make its way to the top of the 'fix' queue when it all seems to be tied to use of the DST calculation offset.
http://athena.trixology.com/index.php?topic=1901.0
-
Took a look at this yesterday - should be fixed in the next release.
-
Sorry for re-opening an old thread, but I was wondering if this bug was ever fixed. The reason I am asking is that since daylight saving time started last weekend, I am seeing timings one hour out on reports like the monthly report. For example, today it's showing that the highest temperature was at 23:00 - it is currently 10:35 here.
Have I missed something? Do I need to change anything in preferences?
-
You're running a beta (2.3.1)?
It was fixed, then in 2.3.1 I rewrote the code that grabs the times as some were off by a random amount (+/- 2 hours) and broke it again.
Should be fixed in the next 2.3.1 build (see the 2.3.1 beta thread). The next released version will be 2.3.0 which will be released shortly.
-
Thanks for your quick response. That explains a lot. I only upgraded to the latest beta version yesterday, which is probably why I've started to see the errors.
Looking forward to the next version.
-
I see it's already posted for downloading.
Hopefully 2.3.0, Build 86 will put this persistent gremlin/irritant to bed forever.
-
Yep, that fixed it for me.