Well ... the 73 is what triggers the WSJT-X log panel. As far as the
multiple RRR/RR73s, the RRR users send DO expect a 73 from you (at least
the system does), the RR73 users have no clue.
Neil, KN3ILZ
On 5/21/2020 6:17 PM, Al Pawlowski wrote:
Actually, just discovered that WSKJTx already almost does this.
Putting a blank line in the tx5/custom message window during a QSO
will cause a tx disable after tx4 - whether you sent the first CQ or
not. However, the auto-log window popup does not work unless a
tx5/custom non-blank message is sent.
BTW, in testing this on 4 QSO’s, all 4 of my QSO partners sent
multiple RRR/RR73’s (after not getting a 73 from me).
Al Pawlowski, K6AVP
Los Osos, CA USA
Begin forwarded message:
*From: *Al Pawlowski <k6...@almont.com <mailto:k6...@almont.com>>
*Subject: **Re: Clicking on RR73 produced wrong TX response msg*
*Date: *May 21, 2020 at 09:37:11 PDT
*To: *wsjt-devel@lists.sourceforge.net
<mailto:wsjt-devel@lists.sourceforge.net>
A nice new feature for WSJTx might be to not reset the
custom (tx5) message (to CS 73) for a QSO and instead skip, or end
with, tx5 depending on the message content, i.e. a blank (or ***
say) in the window would mean skip - it might even make sense to make
the skip message the default.
Al Pawlowski, K6AVP
Los Osos, CA USA
On May 20, 2020, at 16:52, wsjt-devel-requ...@lists.sourceforge.net
<mailto:wsjt-devel-requ...@lists.sourceforge.net> wrote:
Date: Wed, 20 May 2020 16:51:57 -0700
From: Paul Kube <paul.k...@gmail.com <mailto:paul.k...@gmail.com>>
To: WSJT software development <wsjt-devel@lists.sourceforge.net
<mailto:wsjt-devel@lists.sourceforge.net>>
Subject: Re: [wsjt-devel] Clicking on RR73 produced wrong TX response
msg
On Wed, May 20, 2020 at 2:05 PM Gary McDuffie <mcduf...@ag0n.net
<mailto:mcduf...@ag0n.net>> wrote:
If you call letting him know that you got his acknowledgement of your
report a courtesy, I guess so. I call it a necessity in order to
allow him
to move on. If I don?t send the 73, it means I didn?t get his
RR73. If he
doesn?t finish, he isn?t in the log.
If you didn't get his RR73 (Tx4), certainly the thing to do is to resend
your report (Tx3), no?
On the other hand, if you did get his RR73, you can consider the QSO
completed, and respond in whatever way you want. At least, that's
the view
I've come to after using the FT* modes since they were invented. Was it
"really" a QSO? I'll let LoTW or the contest logcheck software sort
it out.
A special case is when I see a station I've worked sending RR73
again. That
shows they're probably expecting a 73 from me and didn't get it. So
in that
case I'll send 73 (Tx5, which is totally customizable, there's even a TX
Macros page in Settings that lets you create a whole library of
them). But
that almost never happens anymore.
--
This email has been checked for viruses by AVG.
https://www.avg.com
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
