Hi !
I'm not WSJT developer but I have understood this mailing list is the
right place for suggestions.
First of all I would like to thank the whole team for excellent work.
Specially the splitting operations (Hold_TX & key+clicks) are now just
perfect. Ḯ'm testing with r8164 at the moment.
How ever there is still one minor thing that I would like to see changed.
Either user by select, or hard coded. I would prefer hard coded way.
When you answer to CQ on the same frequency as caller, but caller does
not take you, your TX is disabled. That is good.
But if you answer by using split frequency you TX stays enabled (until
timeout!).
I think TX should be disabled in any case if answer goes to someone
else. No matter what frequency TX is using for answer.
It would not prevent calling CQ-caller again during his other qso, but
it would then require setting TX enabled again for every separate period.
That would prevent qso_machine_style tires : "I'll keep calling him
until TX timeout, maybe he takes me next.."
If we think that FT8 is used in a DX operation, additional broadcasts
will fill the band and make the copying on the DX side harder.
Please consider extending then TX disable-"if not for me" also to
situation when split frequency answering is used.
Thank you !
--
Saku
OH1KH
------------------------------------------------------------------------------
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
