On 04/08/2017 02:22, James Shaver (N2ADV) wrote:
I had a FT8 QSO with W7PSK earlier (thanks!) where I was calling CQ, he responded to me,
we went through the sequence, he sent his 73 and then moved off to call CQ elsewhere on
the band. Unfortunately, my 73 pulled his TX back to where I was causing him to
accidentally start calling CQ where he had just answered me. Would it be simple to have
the TX not be pulled back upon receipt of the 73? I know he could have unchecked
"Call 1st" and avoided being pulled back but then if someone had answered him
after calling CQ, he would have to manually answer.
Hi Jim,
I can reproduce that behaviour if I have him with "Lock Tx=Rx" checked.
The more use cases I test with auto-sequencing the more I am growing to
dislike "Lock Tx=Rx".
I will see if I can work out how to stop this sort of thing happening.
73
Bill
G4WJS.
------------------------------------------------------------------------------
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
