I think it's a case of semantics. If you push "Tx" button on rig it starts
Tx...."Enable Tx" sounds a lot like that.
"Enable Tx Next" might be more appropos. Even then if you Enable during a Tx
period it starts but at least that still meets the "Next" behavior I think. Or
"Tx Allowed".
de Mike W9MDB
From: Bill Somerville <g4...@classdesign.com>
To: wsjt-devel@lists.sourceforge.net
Sent: Monday, January 2, 2017 10:43 AM
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
On 02/01/2017 16:40, ANDY DURBIN wrote:
That assertion is simply not true. I keep v1.3 r3673 on my computer so I can
check things like this. In r3673 pressing the lit "Enable Tx" button while
transmitting a message does stop the message transmission! "Enable TX" used to
be just that - Enable TX - and if it was not lit then no TX was possible.
Hi Andy, ok, so are you saying that you want to revert to having no "Halt Tx"
button and have the "Enable Tx" button have two functions that cannot be
separated? 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
------------------------------------------------------------------------------
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
