On 20/07/2017 18:23, Black Michael via wsjt-devel wrote:
The problem I think that can occur is when you use, for example,
JTAlert to tell you who you need.
If you enter a QSO but don't get a QSL I think JTAlert will still show
it as a B4 entry which, if you don't have B4's being show, you won't
see on JTAlert call slots. So if you confirm, but your partner does
not, then you may never recognize them again.
One could argue that's JTAlert's responsibility and perhaps JTAlert
should check the LOTW/eQSL status to say "hmmm...not confirmed so
still show them".
I'll ask Laurie about that one.
Hi Mike,
you have a valid point and it is true for DX Lab Suite DXKeeper as well.
It does not consider a dupe of an unconfirmed contact worthy of working
again to try for a confirmation. The assumption there is that they do
not QSL. OTOH if they do send a confirmation it is all is ok. If they
haven't logged the contact then at least they might try for another QSO
but if they are rare and I am not then that is a slim chance.
73
Bill
G4WJS.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
