Agree 100%. The number of ops who refuse to be control operators and just log and move on because, “the software didn’t tell me the QSO is complete” is staggering. On Oct 22, 2023, at 1:06 AM, Ed W0YK via wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote:
+1
-------- Original message -------- From: Ron WV4P via wsjt-devel <wsjt-devel@lists.sourceforge.net> Date: 10/21/23 13:02 (GMT-08:00) To: WSJT software development <wsjt-devel@lists.sourceforge.net> Cc: Ron WV4P <wv4...@gmail.com> Subject: Re: [wsjt-devel] No 73 allowed after RR73?
I wish this was THE way, the useless final 73 should have never existed and is the bain of the mode.
Ron, WV4P
WSJT-X ver 2.6.1, Win 8.1.
I have observed several times that I could not complete a QSO by sending 73 after I had received an RR73. This is expected operation with F/H active but not when F/H is not active. I suspect that something is latched in software if F/H mode has been used
but is then exited and WSJT-X is not re-started.
Has anyone else seen this or have an explanation?
73,
Andy, k3wyc
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
|
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
