Arrghjhh...I was looking at a network dump and confusing nibbles for
bytesnever mindsigh.
de Mike W9MDB
From: Bill Somerville
To: wsjt-devel@lists.sourceforge.net
Sent: Wednesday, May 24, 2017 9:40 AM
Subject: Re: [wsjt-devel] Small patch
On 24/05/2017 15:28, Black
On 24/05/2017 15:28, Black Michael wrote:
But check out 5089
|// In 5.2 we switched to using Qt::TimeSpec and added offset support
dateAndTime = getDateTime(dateTime.d); out << dateAndTime <<
qint8(dateTime.timeSpec());|
||
|It's milliseconds now instead of seconds so needs 64-bit.|
Hi Mike
From: Bill Somerville
To: wsjt-devel@lists.sourceforge.net
Sent: Wednesday, May 24, 2017 8:08 AM
Subject: Re: [wsjt-devel] Small patch
On 24/05/2017 13:24, Black Michael wrote:
The QTime should be quint64 and not quint32 in NetworkMessage.hpp
Hi Mike, that's not correct. The corr
On 24/05/2017 13:24, Black Michael wrote:
The QTime should be quint64 and not quint32 in NetworkMessage.hpp
Hi Mike,
that's not correct. The correct information can be found here:
http://doc.qt.io/qt-5/datastreamformat.html
and coded as:
http://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib
Was reviewing the logging message for Rick Ellison and N1MM and noticed a small
documentation error.
The QTime should be quint64 and not quint32 in NetworkMessage.hpp
* QDateTime: * QDate qint64 Julian day number *
QTime quint32 Milli-seconds since midnigh
