I have v 2.0.0-rc3 running on a Windows 10 Pro. JTAlert feeds the logging to Log4OM reliably.
This afternoon on a very crowded waterfall at 14.074 I had several busted QSOs where the calling station was covered up in QRM before the call could be completed. Instead of sending my signal report continuously until the TXWD timed out, I used F4 to clear the QSO and went back to calling CQ. The next QSO was logged with the time of the busted QSO, not the correct current QSO time.
First couple of times I was annoyed but thought it was just a glitch between JTAlert & Log4OM. This happened several more times, I finally opened & looked at wsjtx.log and found the incorrect QSO time recorded in wsjtx.log.
Seems to me that the F4 clearing of the DX Call & DX Grid boxes is not also clearing the busted QSO time from the logging function?
73, Doug KV4ZY
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
