Guard the condition with an assertion and bring the program down when it
happens. That will prevent transmission on the wrong cycle and probably bring
you diagnostic information that will lead you to the error. Regardless, the
assertion should always be there, since it is so important to avoid exactly
what I wound up doing.
Dave / NX6D
________________________________
From: Joe Taylor <j...@princeton.edu>
Sent: Friday, June 29, 2018 7:12:28 PM
To: WSJT software development; David Fisher
Subject: Re: [wsjt-devel] Transmitting at the wrong time in Hound mode
On 6/29/2018 8:26 PM, David Fisher wrote:
> I have the “ALL LOG” excerpt of this if you want to see it. You’ll have
> to take my word on the rest.
>
> The code version is 1.9.0-rc4 R8642. I built it from source a while back.
Version 1.9.0-rc4 was a program version made available for short-term
beta testing. It is NOT a general availability (GA) release of WSJt-X.
None of our "-rc#" releases are suitable for long-term use.
You should upgrade to the GA release on the WSJT Home Page, Version 1.9.1.
As I have written elsewhere: When you're in Hound mode, the *Tx
even/1st* box (grayed out) must NOT be checked. It's supposed to be
impossible for this to happen, but several people have claimed that it
can. If you find the box is checked: exit Hound mode, clear the
box, then re-enter Hound mode.
And this is important: if you can figure out how to cause *Tx even/1st*
to be checked while in Hound mode, please send me an exact series of
steps that will do so.
-- 73, Joe, K1JT
------------------------------------------------------------------------------
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
