Hi Edfel,
sorry I was not clear. The edits I am referring to are to the Contest
Log window rows. As it stands in WSJT-X v2.0.0 RC5 edits to fields in
the Contest Log window table are not committed until you change the
focus to another row. Until you do that pending edits will block the
addition of a new QSO. This was not intended and it will be fixed.
73
Bill
G4WJS.
On 02/12/2018 02:29, Edfel Rivera wrote:
Hi Bill:
I filled those fields (operator, name) because fields were empty (not
populated by the program) and because program pop up message was
Invalid QSO. Was a way to test if that empty fields were the reason
for the error. Anyway, Invalid QSO popups keeps happening and they
are empty at those fields.
Thanks.
Edfel
On Sat, Dec 1, 2018 at 9:03 PM Bill Somerville <[email protected]
<mailto:[email protected]>> wrote:
Hi Edfel,
I am fairly certain that the logging lockout when al the required
fields are populated is related to unsaved edits to the contest
log window. As it stands you have to move to another row to commit
any edits, then you can log a new row.
I am surprised how many reports of this there are, what is
requiring editing on the contest log window?
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
