I've also had this issue plus another: I believe in earlier versions if I DID NOT check the respond to first call and I was answering CQ callers, after I sent 73 the program would leave the 73 tab in place and NOT MOVE to CQ tab.
If I'm working others and NOT CALLING CQ, then I do not want the Auto Seq to move to CQ at the end of my QSOs - it doesn't make any sense to do that. Again, I believe that at some time in the past the program would not move to CQ tab unless the 1st call box was checked. Once the other station does not reply as 'expected' by the Auto seq it's very challenging to get the proper response activate quickly. In fact, even if I quickly click on the correct tab to send the appropriate response, the Auto seq overrides my entry and sends what it wants. Stephen - K6SJT Fallbrook CA _____ From: Al Pawlowski [mailto:k6...@almont.com] Sent: Tuesday, November 20, 2018 8:45 AM To: WSJT software development Subject: Re: [wsjt-devel] General issue : The RRR / 73 "loop" What I have started doing is always going back to the tab after my final response (RR73 or 73), re-enabling and re-selecting the final message and then sitting with my mouse of the disable tx button to kill the tx if the other party responds like they got my last message. At least in non-contest mode, seems like it might be better for the sequencer not to advance and kill the tx enable, i.e. let the operator hit kill. Al Pawlowski, K6AVP Los Osos, CA USA Date: Tue, 20 Nov 2018 09:02:55 +0000 From: Stephen Ireland < <mailto:vk3...@hotmail.com> vk3...@hotmail.com> To: WSJT software development < <mailto:wsjt-devel@lists.sourceforge.net> wsjt-devel@lists.sourceforge.net> Subject: [wsjt-devel] General issue : The RRR / 73 "loop"
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
