I've had no problems other than the Version 2.xx DST issues highlighted in another thread.
Please raise it as a bug in the bugs forum along with any screenshots you have
I'm pretty sure you have it on your list of bugs to be squashed, Stu, at least you told me it was when I sent some notes and screen shots earlier during the development. I was just trying to get a feel for when the DST bug might make the way to the top of the list (
http://athena.trixology.com/index.php?topic=1479.0) since some of the recent builds were squashing 'nits' and this is a bit more important for folks who use the data beyond hobby purposes. Anyway, as a memory jogger ref the shots below, according to the WC Data Viewer yesterday was a 2
5-hour day...it started at 2305 hours (actually the day prior) and ended at 2359 hours.
I'm not a programmer but I assume you internally use GMT time because once the date passes to the next GMT date, the data gets magically sorted out again. Unfortunately, that doesn't help folks several time zones away who use the data in real time.
And as I noted in the thread referenced above, this also affects the Query feature outputs...but not always and I haven't been able to sort out the common parameter.
I'll also move this over to the bug sub-forum per your request.