Gary,
I'm fairly sure it has always been this way, even before v1.8 and FT8.
I see to remember that it was the reason the last CQ caller's 73 was
added to the 'conversation', to trigger the Log QSO window. Adding
the RR73 as an option in v1.9 was to acknowledge what a log of CQ
callers were actually doing to avoid that last 73 and trigger the Log
QSO dialog.
Neil, KN3ILZ
On 11/27/2018 7:04 PM, Gary Hinson wrote:
Hi.
The ‘prompt me to log QSO’ setting only seems to do its thing when I
send a 73 message – specifically, it seems, I have to send a free-text
message containing the string “73”. So, if I send a custom message to
conclude a QSO, one that doesn’t include 73, I’m not prompted to log
the QSO.
I know I can still hit the Log QSO button … provided I’m aware of the
issue and log it before the next caller’s info causes the messages to
be generated for the next QSO.
I’m wary of stirring up the ‘when is a QSO not a QSO’ argument yet
again but personally I would rather be prompted to log the QSO as I am
sending or after I have sent an R message (Tx3 or Tx4, both RRR and
RR73 forms), or at the very least when I send any free text message
after having sent Tx3 or Tx4, not necessarily one containing “73”.
73
Gary ZL2iFB
PS For bonus marks, I’d love the Tx5 message box to warn me if I
enter too many characters … like perhaps showing the 14^th and later
characters in red, or bold, or italics.
---
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
