On 20/07/2017 18:23, Black Michael via wsjt-devel wrote:
The problem I think that can occur is when you use, for example,
JTAlert to tell you who you need.
If you enter a QSO but don't get a QSL I think JTAlert will still show
it as a B4 entry which, if you don't have B4's being show, you won't
rville <g4...@classdesign.com>
To: wsjt-devel@lists.sourceforge.net
Sent: Thursday, July 20, 2017 9:12 AM
Subject: Re: [wsjt-devel] WSJT-X: How to handle using RR73 as a final message
On 20/07/2017 14:27, Black Michael via wsjt-devel wrote:
> although if autoseq detects the RR73 as the
On 20/07/2017 14:27, Black Michael via wsjt-devel wrote:
although if autoseq detects the RR73 as the prompt to log means they
likely have logged it already which I think is not what should be done.
HI Mike,
there seems to be an aversion to logging a QSO before your QSO partner
can, I don't
ceforge.net>
Sent: Thursday, July 20, 2017 7:19 AM
Subject: [wsjt-devel] WSJT-X: How to handle using RR73 as a final message
Hi All,
we are looking at changing the WSJT-X logic such that a grid message of
the form:
" RR73"
is treated as a sign off message.
This has seve
send my R+dB report
again.
Erik EI4KF.
-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: 20 July 2017 12:18
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Subject: [wsjt-devel] WSJT-X: How to handle using RR73 as a final message
[mailto:g4...@classdesign.com]
Sent: Thursday, July 20, 2017 7:18 AM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Subject: [wsjt-devel] WSJT-X: How to handle using RR73 as a final message
Hi All,
we are looking at changing the WSJT-X logic such that a grid message of th
Hi All,
we are looking at changing the WSJT-X logic such that a grid message of
the form:
" RR73"
is treated as a sign off message.
This has several implications and I need some clarification so that I
can adjust the code. For now I will put aside any potential issues for
holders of
