Everything is hunky-dory nowthanks Joe
de Mike W9MDB
From: Joe Taylor <j...@princeton.edu>
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Sent: Tuesday, November 22, 2016 6:44 PM
Subject: Re: [wsjt-devel] r7329 breaks JTAlert
Mike --
Please see if
It's helpful to be able to click on a CQ in JTAlert rather than in the decode
window in WSJT-X when the band is very busy. It is frustrating when you go to
click on a CQ and the decodes keep scrolling the target station away (more than
once I've ended up clicking on the wrong station).
Jim S.
On 23/11/2016 11:05 AM, Joe Taylor wrote:
> Why would I want JTAlert to start a QSO?
JTAlert has always had this ability since the introduction of the UDP
interface. Double-clicking a Callsign (that is CQing) in JTAlert will
send the appropriate UDP "Reply" packet to WSJT-X which sets WSJT-X to
re development <wsjt-devel@lists.sourceforge.net>
> *Sent:* Tuesday, November 22, 2016 6:05 PM
> *Subject:* Re: [wsjt-devel] r7329 breaks JTAlert
>
> Why would I want JTAlert to start a QSO?
>
> On 11/22/2016 6:23 PM, Black Michael wrote:
> > The change in r7329
: Joe Taylor <j...@princeton.edu>
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Sent: Tuesday, November 22, 2016 6:05 PM
Subject: Re: [wsjt-devel] r7329 breaks JTAlert
Why would I want JTAlert to start a QSO?
On 11/22/2016 6:23 PM, Black Michael wrote:
> The
Why would I want JTAlert to start a QSO?
On 11/22/2016 6:23 PM, Black Michael wrote:
> The change in r7329 to fix the Autoseq disables JTAlert's ability to
> start the QSO. Clicking in JTAlert will show the CQ message in the
> receive window but no longer enables "Enable Tx".
> r7328 works fine.
The change in r7329 to fix the Autoseq disables JTAlert's ability to start the
QSO. Clicking in JTAlert will show the CQ message in the receive window but no
longer enables "Enable Tx".r7328 works fine.
de Mike W9MDB
