Hi Joe, Hope you had a decent holiday season. Hopefully 2022 will be better than 2021. In testing WSJT-X Ver 2.5.4 with my program QLog as its used by blind hams I ran into a problem where when I decided to Halt TX and then clear the standard messages (1-4) by sending a "F4" from within my program to WSJT-X the Log QSO prompt popped up. That same thing happened when I manually halted Transmission then Press F4 directly in WSJT-X. Tracing the problem, I found that the Alternate Key Bindings options was turned on. I know that I did not do that manually. Based on what I found in the two examples (see below), I am wondering if somewhere along the linesduring one of the installations of the last 3 versions 2.5.2, 2.5.3 or 2.5.4 that Alternate Key Bindingoption was automatically set to true. In any event, I think that the Statement in Section 7.4 should be clarified to state that the F4would only work if the Alternate Key Binding is set to true in the WSJT-X settings. Otherwise,they will clear the messages and potentially lose the QSO data. I do believe that If I never received any response (either a TX2 or TX3), to my first outgoing message, WSJT-X should disable the ability send a RR73 and popup a Log QSO prompt.
Bottom of Section 7.4 of the online user manual your will find: Log a QSO when you send RR73 or 73 if you are reasonably confidentit will be copied. But be sure to watch for any indication that itwas not copied, and then take appropriate action. For example, ifyou receive the Tx3 message (R plus contest exchange) again, hit F4to re-send your RR73. On keyboard shortcuts screen you will find: F4 Clear DX Call, DX Grid, TX Messages 1-4 (Alt: transmit Tx4) 73, Sam W2JDB
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
