In our case the DX call and grid were not cleared. It was the jump to TX6 and disabling TX that were the issue.
Agreed it is only two mouse clicks to restart a repeat RR73 message, but having to do it repeatedly in the contest prompted the comment, in each case then starting late into the period thus reducing the chance of QSO partner decoding it. The current behaviour seems to be at odds with having Disable TX after 73 unchecked. Accept that RR73 is not 73 of course, but the issue is the same for contest operating. Charlie > <html><body><span style="font-family:Verdana; color:#000000; > font-size:10pt;"><div>Bill,</div><div>As I think some others have been > reporting, the unchecking of "Clear DX call and grid after logging" seems > to be broken on my Windows version of rc5. Mine is unchecked, yet it > continues to clear the DX call and grid, jump to TX6, and toggle TX Enable > off whenever mine sends RR73. This has been continuous through many > closings and restarts of rc5 with the box unchecked. I have also tried > unchecking Call 1st at the beginning of the QSO during my TX of the other > station's report, no difference seen > here.<br></div><div><br></div><div>I'm not fast enough to recover in time > to continue the QSO when the other station sends my report again because > he did not copy my report, but mine has already sent RR73, cleared the DX > Call and grid, and toggled TX off anyway. Is this just the Windows version > problem, or are other versions not having the same problem? I am hoping > this has been fixed in the GA release?<br></div><div><br></div><div>73 de > KV4ZY<br></div><div><br></div> > <blockquote id="replyBlockquote" webmail="1" style="border-left: 2px solid > blue; margin-left: 8px; padding-left: 8px; font-size:10pt; color:black; > font-family:verdana;"> > <div id="wmQuoteWrapper"> > -------- Original Message --------<br> > Subject: Re: [wsjt-devel] Please Clarify How to Operate with Sticky > Tx4<br> > & Tx5 and not advance to Tx6<br> > From: Bill Somerville <<a > href="mailto:g4...@classdesign.com";>g4...@classdesign.com</a>><br> > Date: Thu, December 06, 2018 5:56 pm<br> > To: <a > href="mailto:wsjt-devel@lists.sourceforge.net";>wsjt-devel@lists.sourceforge.net</a><br> > <br> > On 06/12/2018 17:26, Stephen Taylor - K6SJT wrote:<br> > > I think I recall from last year if the I placed a check mark in the > 'Call<br> > > 1st' box the program would move down to Tx6 CQ at the end of a > contact, BUT<br> > > if the box was NOT CHECKED the Auto seq would remain on the Tx5 73 > and NOT<br> > > ADVANCE to Tx6. The advantage of that was if I didn't get a return 73 > I<br> > > could quickly press 'Enable Tx' to resend my 73. Bill, am I recalling > this<br> > > wrong?<br> > ><br> > > Bill, because I operate >95% of the time Responding to CQs, not > Sending CQs,<br> > > I would like some way to have the Tx 4 and/or Tx 5 remain in place > (sticky)<br> > > at the end of each contact rather than advancing to Tx 6 CQ.<br> > <br> > Hi Steven,<br> > <br> > if you uncheck the option "Settings->Reporting->Clear DX call and > grid <br> > after logging" then you get what you want and can be also ready to call > <br> > CQ or call another station. You can clear down the DX Call, DX grid, and > <br> > messages manually using the F4 keyboard shortcut. Agreed you need to <br> > click twice to reselect Tx4 (RR73) or Tx5 (73) and re-send it, you are > <br> > also only two clicks away from calling CQ on a new Tx offset or a <br> > double-click away from calling another station. That seems a fair <br> > balance of usability between calling CQ, always replying to CQ calls, <br> > repeating a message to complete a QSO, or starting a new QSO with <br> > another station calling CQ. None of the options takes more than two <br> > mouse clicks.<br> > <br> > 73<br> > Bill<br> > G4WJS.<br> > <br> > <br> > <br> > _______________________________________________<br> > wsjt-devel mailing list<br> > <a > href="mailto:wsjt-devel@lists.sourceforge.net";>wsjt-devel@lists.sourceforge.net</a><br> > <a > href="https://lists.sourceforge.net/lists/listinfo/wsjt-devel";>https://lists.sourceforge.net/lists/listinfo/wsjt-devel</a><br> > > </div> > </blockquote></span></body></html> > > _______________________________________________ > 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
