Hi Dave,
ok, let's assume that's what happened, at least until we get other
reports of the same inconsistency that cannot be attributed to a band
change before completing of a logged QSO. As the time a QSO is logged is
not recorded we cannot be 100% sure that is what happened in your case
but I think it is very likely.
Thanks for the report, especially as it revealed another related issue
which turned out to be a defect.
73
Bill
G4WJS.
On 17/09/2019 20:46, Dave Slotter, W3DJS wrote:
Bill,
Your explanation makes sense. According to the ADIF log, I worked W3L
on 40 meters, and according to the GUI screen capture, I had switched
afterwards to 20 meters. (I do not recall the exact order of clicking
"OK" on the Log window, but somehow I don't think I would have
switched bands before confirming the QSO. This would be inconsistent
with how I operate -- I think.)
Thanks for looking into this.
73,
--
Dave Slotter, W3DJS <https://www.qrz.com/db/W3DJS>
On Tue, Sep 17, 2019 at 3:05 PM Bill Somerville <g4...@classdesign.com
<mailto:g4...@classdesign.com>> wrote:
Hi Dave,
ok, here's what I think may have happened. You were trying to work
W3L across multiple bands and had worked them on 40m but had not
yet clicked "Ok" on the pending "Log QSO" window until after you
had switched to 20m and copied there CQ call on that band at
21:11:45. At that point you completed the logging of the 40m QSO
which as expected updated the internal database of stations worked
etc. Hence the next CQ from W3L was no longer highlighted as a new
call.
Is this consistent with what may have happened?
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
