Not sure this is the proper place for this so if it's not please route
it wherever it needs to go.
WSJT-X 1.3 r3673, JTAlert-X 2.5.6, XP SP3
The WSJT-X User Guide Chapter 8.7 states, among other things;
/Your “worked before” status (according to log file wsjtx_log.adi) is
flagged with a single character and a change of background color, as
follows://
//
//! (bright green)-New DXCC entity//
//~ (mid green)-You have already worked this DXCC entity but not this
station//
//(dull green)-You have previously worked the calling station//
//
//The program does not distinguish between modes, but it does
differentiate between bands.//
/
Over the past few days I have observed that WSJT-X has reported a number
of CQ calls as having been previously worked while JTAlert-X reports the
same calls as having not been previously worked. Investigation as to why
this may be so led me to the following.
Using my QSO with K5JC as an example I am able to locate my logged entry
in wsjtx_log.adi and the message entries representing the exchange in
the ALL.TXT file. This QSO took place on 20m. However, I am now working
on 15m and WSJT-X reports K5JC as having been previously worked. This is
all well and good since the worked before status is obtained from the
log.adi file but the user guide claims that WSJT-X differentiates
between bands. If that was the case K5JC should not have been flagged as
having been worked before on the 15m band.
Or am I missing something?
--
Brian - KB6LZJ
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
