Not sure where to post this, but only the TEST in "CQ TEST xxxxx xxnn" is being highlighted as if it was an unworked callsign during the VHF contest while using WSJT-X along with N1MM (using the WSJT-X Decode List window). I start with a fresh log (actually a rig instance), so new callsign highlighting in WSJT-X is enough for all but the few SSB contacts I have made. This behavior wasn't present during the RTTY Roundup as RU wasn't flagged as an unworked callsign. For those operators not using contest mode, the "CQ xxxxx xxnn" is being highlighted correctly.
I have attached a snapshot of the WSJT-X and WSJT-X Decode List windows during the contest showing a few of these TEST highlights. My system is as follows: HP Notebook 2.00 GHz 64-bit 8.00GB RAM O/S: Windows 10 Home, version 1803 (OS Build 17134.523)WSJT-X v2.0.0 784f75N1MM v1.0.7467.0Rig: Yaesu FTDX3000 (USB to WSJT-X only) 73 David KC2WUF
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
