clear. thanks a million Bill for the info. cheers serge Envoyé de mon iPad
> Le 13 déc. 2018 à 19:16, Bill Somerville <[email protected]> a écrit : > >> On 13/12/2018 17:37, F6BHK wrote: >> Hello, >> >> A quick question on "Status" UDP messages sent by WSJT-X v2. >> >> WSJT sent me a message where the length of the DXCall is -1. This is new for >> me: I didn't notice this behavior in v 1.9.1. >> >> Here is an example of the frame after a conversion to hex : >> >> [0000000b57534a542d58202d20763200000000009aa9c000000003465438ffffffff000000032d313500000003465438000001000005dc000005dc00000005463642484b000000064a4e32346978ffffffff00ffffffff0000] >> >> >> See after the mode (FT8) I have FFFFFFFF, then follows the report in UTF8 >> format. >> >> It looks to me I should have received a UTF8 string instead of FFFFFFFF. >> Well I might have misinterpreted the NetworkMessage.hpp contents where >> DXCall is UTF8 formatted between the mode and the report. >> >> Or is it a way to deal with empty string? >> >> Thanks for your help >> >> Cheers >> >> Serge > > Hi Serge, > > as documented here http://doc.qt.io/qt-5/datastreamformat.html the > serialization of a QString variable can have a length of 0xffffffff (it is > unsigned) and that signifies a null value. You may wish to treat zero-length > and null strings as equivalent as mentioned in the documentation here: > https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/NetworkMessage.hpp#l42 in > the second paragraph down. > > A null or empty DX Call field in s a status update simply means the DX Call > field is empty or has just been cleared. > > 73 > Bill > G4WJS. > > > > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
