On 30/05/2019 15:25, Bill Somerville wrote:
On 30/05/2019 15:15, Bill Somerville wrote:
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.
Hi Mike and Jari,
I will qualify that. For compound calls the above is true but for
other non-standard calls it is not. There is a defect that causes the
option to skip Tx1 to be allowed for non-standard non-compound calls,
in that case a double-click of a CQ decode will incorrectly send Tx2.
Despite that users with non-standard non-compound calls still need to
understand the implications and should not select the option to skip Tx1.
73
Bill
G4WJS.
Also as Reino, OH3MA, has just pointed out, the DX may have attempted to
tail-end Jari's previous QSO by double-clicking a decode from him. That
too would set up Tx2 as the Tx message when the option to skip Tx1 is
enabled. It is the same problem, either way WSJT-X should not use Tx2 as
the response to a double-clicked decode whether the option to skip Tx1
is enabled or not.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
