On 25/11/2017 13:17, Black Michael via wsjt-devel wrote:
There's a problem logging with JTAlert (and perhaps other apps too) if
you leave the logging dialog box open and change the active call sign.
JTAlert maintains the additional logging info by the active call
sign....like country....so you may end up logging the wrong country.
There's a potential fix for WSJT-X that's not too onerous....simply
disalow changing the DX Call while the logging box is open...simply
disable it (to make it obvious) and reenable after logging.
I'll be happy to make that patch if deemed appropriate.
de Mike W9MDB
Hi Mike,
that issue is not due to WSJT-X and I don't think a change in WSJT-X is
warranted. There is nothing wrong with starting a new QSO before logging
the prior one, no information is lost as the Log QSO window holds the
information until the "Ok" button is pressed.
I believe the issue is that JTAlert looks up the country for the call
sign, surely it can do that for the call sign in the Log QSO UDP record,
in fact it really should as a QSO may have been completed with a
compound call holder without their prefix/suffix being exchanged during
the QSO even though it is known from prior decodes. The user could quite
reasonably log a prefix or suffix that was never in the DX Call field.
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
