Laurie
have you considered adding other modes for WAS track? or was it always
JT65/JT9?
------ Original Message ------
From: "Laurie, VK3AMA" <_vk3a...@vkdxer.net>
To: wsjt-devel@lists.sourceforge.net
Sent: 7/11/2017 1:19:51 PM
Subject: Re: [wsjt-devel] Distribution
On 12/07/2017 4:10 AM, Bill Somerville wrote:
RR, Laurie. My mistake as mentioned in the other post. I will claim I
did it so developers of other software get a head start.
BTW I did some basic tests with JTAlert using it to initiate MSK144
and FT8 QSOs from alerts. This was necessary as I fixed a few
problems with the content of the UDP messages. Apart from the already
discussed and deferred issues of dealing with shorter than 60s T/R
periods both worked just fine, thanks.
73
Bill
G4WJS.
Hi Bill,
Thanks for the UDP test feedback.
I am still considering how best to handle the 15s T/R period of FT8.
Regarding the broken JTAlert docking with WSJT-X when a configuration
switch is made, that is now fixed for the next release. (I used the
Close event to set a flag indicating that the hWnds needed to be
refreshed which are then updated on the next Heartbeat).
de Laurie VK3AMA
------------------------------------------------------------------------------
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