On 17/02/2017 16:05, Black Michael wrote:
I see the patch set Qt::UTC.
I was getting UTC times on my system. Do you perhaps have an
environment var that changes the time zone that Qt is using?
I can't find any reference on environment variables overriding
defaults. I'm running on Windows 10.
And since you set UTC after the times have been parse I'm a bit
confused as to the effect. I guess it fixed some problem on your system?
Hi Mike,
I noticed the issue when writing some AutoIt code to demonstrate how to
do UDP multicast message reception. The problem was that the code in
logqos.cpp was breaking a QDateTime UTC object into separate date and
time strings then rebuilding a QDateTime object from them. The problem
is that the resulting QDateTime object was incorrectly flagged as local
time despite the time actually being UTC. All I have done is reset the
UTC flag so that the time object is correct and consistent. I was just
correcting sloppy programming, probably would have been better if the Qt
QDateTimeEdit widget had been used rather than messing around with
splitting and re-parsing the QDateTime objects.
This probably mattered little except that the QDateTime object was being
sent in the UDP "QSO Logged" message, so recipients in theory should
misinterpret the time as local for their location. I have no idea if
JTAlert etc. actually take any notice in the timespec component of the
QDateTime field but it was incorrect and ow it is correct.
73
Bill
G4WJS.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
