Mike,
double-clicking a CQ decode will do the right thing. The DX in this case
must have taken deliberate action to send Tx2, that is their mistake,
not our problem to fix.
73
Bill
G4WJS.
On 30/05/2019 14:27, Black Michael via wsjt-devel wrote:
How about for hashable calls we do a a last-time-TX1-transmitted. And
if TX2 is started without ever transmitting TX1 then a warning dialog
pops up to 'splain things.
Mike
On Thursday, May 30, 2019, 8:23:21 AM CDT, Bill Somerville
<g4...@classdesign.com> wrote:
On 30/05/2019 14:13, Black Michael via wsjt-devel wrote:
> Maybe WSJT-X should ensure such users send CQ once in a while...that
> would be non-intuitive. A simple message in the decode window or such
> that said "CQ needed, non std call" with a help file reference to
> 'splain things.
>
Hi Mike and Jari,
there is no need to send CQ, the Tx1 message sent in reply to a CQ will
also populate the hash table. It seems in this case that the DX has
started with the TX2 message, that will only work if the CQ caller has
copied another QSO involving the DX which is not a very good strategy as
they have no way of knowing if that is so.
Stations with non-standard calls using F8, FT4, or MSK144 must
understand how hash codes work if they are going to be successful in
making QSOs.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
