Nice thinking outside the box....but there are a few pedantics who won't confirm a QSO if you fall outside the standard exchange....they've mentioned it before on this list (or one of the others). So best solution is education...so I think a little in-your-face of the one-time popup...maybe with this verbiage...."FYI....RRR is the last message needed for the calling side of a JT QSO...no 73 is needed...please don't send RR73 or such...see help file"
On Fri, Dec 11, 2015 at 8:34 AM, Chris Sullivan <[email protected]> wrote: > Maybe just add an option to display RRR 73 whenever the RRR message is > received, and to show RRR as RRR 73 on the transmit side, without actually > changing the protocol. I’m not up on the structure of the JT65 messages but > I suspect that RRR is just a single bit set somewhere in the message, or > perhaps an unused grid code, so the interpretation is up to the program. > > > > RR73 does drive me a little crazy on HF as the standard response to it is > to send a signal report. > > > > 73, > > Chris > > > > <https://www.avast.com/lp-safe-emailing?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> This email has been sent from a virus-free computer protected by Avast. www.avast.com <https://www.avast.com/lp-safe-emailing?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
------------------------------------------------------------------------------
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
