Wouldn't this logic work?
#1 is73 -- current logic#2 ignore if has2calls and not mybasecall
So that's a standard 73 between two parties not including me. Is there a 73
that has two calls that would be valid and not contain my call?
Mike
On Wednesday, June 5, 2019, 6:34:40 AM CDT, Bill Somerville
<[email protected]> wrote:
On 05/06/2019 12:21, Black Michael via wsjt-devel wrote:
Was in middle of QSO with K8HC and he had to give a 73 to somebody else.
Autosequence moved me to TX1 instead of staying on TX3. So I had to click TX3.
Seems to me that lines that contain a different call then the QSO in progress
and not my call should not affect sequencing at all.
de Mike W9MDB
Hi Mike,
this is a tough issue to deal with. Currently any message on or very close to
the Rx frequency that contains the word 73 is taken as a signoff. This is
necessary because free text messages are often used at this point on a QSO. The
obvious solution is to ignore standard messages that do not contain one's call
but even then with JT65/JT9/QRA64/JT4 etc. there are cases with compound calls
where a 73 message from your QSO partner may not contain your own call. Maybe
we should drop the "any message on frequency containing 73 is a signoff" logic
and force users to react manually to such messages when they are really part of
the current QSO.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
