Numerous times have had people response with sig reports late. They call CQ,
you answer, no response for several tries, you move on to another QSO, the
original one shows back up with a sig report a couple minutes later. Seen this
happening a fair bit.
But, when you double-click on their sig report WSJT-X sets up with Tx 3 instead
of Tx 4.
Removing one line of checking here solves the problem.If you process a message
that has your call in it but the DX Call does not match do we need the logic to
ensure the DX Call matches?Removing it seems reasonable....as long as the
message is addressed to you the processing of next transmission should still be
the same.
de Miike W9MDB
Index: mainwindow.cpp
===================================================================
--- mainwindow.cpp (revision 8748)
+++ mainwindow.cpp (working copy)
@@ -4215,7 +4215,7 @@
{
if (message_words.size () > 3 // enough fields for a normal message
&& (message_words.at (1).contains (m_baseCall) || "DE" ==
message_words.at (1))
- && message_words.at (2).contains (qso_partner_base_call)
+ //&& message_words.at (2).contains (qso_partner_base_call)
&& !message_words.at (3).contains (grid_regexp)) // but no grid on
end of msg
{
QString r=message_words.at (3);
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
