On 02/01/2017 14:54, ANDY DURBIN wrote:
My preference would be to go back to it being an Enable TX function.
Hi Andy,the "Enable Tx" button has always been "Enable auto Tx", in fact the underlying variable name is autoButton and it always has been.
Because the message protocols restrict you to transmitting in only the first or second period of the sequence the only interpretation of that button is transmit when it is next possible to do so. That may be now or at the start of the next suitable period. The "Halt Tx" button is not the antithesis of "Enable Tx" but it does happen to toggle it off, this is because it makes sense to not transmit again after a request to "Halt Tx". Once a transmission is started the "Halt Tx" button is the way to stop it, toggling "Enable Tx" to off does not do that, it never has.
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
