On 25/12/2015 7:52 AM, Bill Somerville wrote:
Hi Laurie,
as I said we do not check for redundant status updates. I will have a
scan through the code and see if any can be easily eliminated but
checking for every field against previous values may be quite tricky.
WSJT-X is largely event driven and redundant events happen all the
time because of the way that GUI event loop messages are generated.
73
Bill
G4WJS.
Bill,
Comparing identically running instances, one 1.5.0 and the other 1.6.0.
The 1.6.0 status packet is 2 bytes longer than 1.5.0
These two packets send @ 50 secs differ by only the last byte. This byte
is a one (1) on the first packet and a zero (0) on the second packet.
This suggested a boolean flag of some sort. Indicating a possible schema
change.
Examining the header of each packet (MagicNo + Schema + MessageType +
ID(rig-name)) shows a schema value of 2 for both 1.5.0 and the 1.6.0
despite the 1.6.0 difference.
Examining the NetworkMessage.hpp file for 1.6.0 shows that the Schema is
now 3, but is *incorrectly* reported in the UDP packets as 2. <-- this
is why I didn't pickup on the schema change in my programs.
The two status packets @ 50 secs correspond to the new status flag
indicating that WSJT-X has started decoding and finished decoding. Now I
know and understand the purpose of those two packets.
After all this, the only defect I can see is an incorrect schema
reported in each UDP packet. 2 instead of 3.
de Laurie VK3AMA
------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
