Date
1 - 1 of 1
Locked Latest WSJT-X Update Appears to Unexpectedly Change "Prompt me to log QSO" Check Box Setting #IssueReport [edited] #IssueReport
Sam Birnbaum
Hi Chuck,
Actually in all previous (prior to 2.5 xx) I only had the "Log Automatically" checked.
When not in contest mode, it still popped up the Log QSO prompt screen.
It was with new version where if you did not have the "Prompt me to log" checked
the prompt did not pop up. According to Bill, they fixed a defect that from
my view point was actually a better implementation.
73,
Sam W2JDB
-----Original Message-----
From: Chuck Adams <cfadams@...>
To: main@WSJTX.groups.io
Sent: Tue, Sep 28, 2021 6:02 pm
Subject: [WSJTX] Latest WSJT-X Update Appears to Unexpectedly Change "Prompt me to log QSO" Check Box Setting #IssueReport
From: Chuck Adams <cfadams@...>
To: main@WSJTX.groups.io
Sent: Tue, Sep 28, 2021 6:02 pm
Subject: [WSJTX] Latest WSJT-X Update Appears to Unexpectedly Change "Prompt me to log QSO" Check Box Setting #IssueReport
I performed the latest update to WSJT-X and did the JTAlert update to 2.50.6 just now.
All is well on the JTAlert side so far. 😊
However, I DID notice that the WSJT-X update unexpectedly changed this setting: ☹
Reporting > Logging > Prompt me to log QSO (check box)
(This box WAS checked in previous version but WAS unchecked after update)
Reporting > Logging > Log automatically (contesting only) (check box)
(This box WAS NOT checked in previous version but WAS checked after update)
(This box WAS checked in previous version but WAS unchecked after update)
Reporting > Logging > Log automatically (contesting only) (check box)
(This box WAS NOT checked in previous version but WAS checked after update)
This “setting flip” resulted in me suddenly not being automatically prompted after I finished QSOs (as I had done for many years previously)
I finally spotted the unexpected change in WSJT-X and corrected it.
This is a minor glitch to be sure, but one that might be worth noting for those who are updating WSJT-X.
Has anyone else seen this unexpected behavior from WSJT-X?
73,
Chuck Adams
KV4VT