Re: [wsjt-devel] WSJT-X V2.0 RC Contest Issues

[David Bean (KC2WUF) via wsjt-devel]

 Joe et al,
Some further observations:   
   - On further review, I had entered '59 NJ' in my exchange for RTTY RU and I 
will need to wait until tomorrow's RTTY RU test for my correcting it to just 
'NJ' to see how this affects my last two bullets in the original post. Note: It 
might be good to do some basic check on the exchange for each contest and alert 
the user to potential corrective action.
   - After finishing the contest mode and switching everything back to what I 
thought was normal FT8 operation (contest None, uncheck both 77-bit only 
boxes), Tx 1 was greyed out and all of my subsequent QSOs skipped Tx 1 and 
proceeded with Tx 2 when I tried to answer a CQ call. This is abnormal behavior 
from my understanding, although I've seen it numerous times on the bands by 
some users.
73 David KC2WUF

On Tuesday, September 25, 2018, 11:37:04 PM EDT, David Bean (KC2WUF) 
 wrote:  
 
 Joe et al,
I was running some RTTY RU contest tests tonight with some friends and noticed 
the following:
   
   - A friend was trying to answer CQ and people calling his CQ without any 
exchange entered in the correct text box and all transmits were <...> form. 
It would probably be advisable to notify anyone operating contest mode without 
an exchange (and if possible an invalid exchange) to get some type of warning.
   - I looked after a few contest QSOs and noticed that the Cabrillo file had 
the 5x9 received report, but had 59 for the sent report. It should be the 5x9 
that I sent.
   - The log QSO text box had no reports (5x9 sent/received) in it during the 
contest and therefore they weren't transferred into my logging program nor the 
ADI file. I did enter the 5x9 for both reports for one of the QSOs and it was 
sent along both chains (ADI and logging program via JT-AlertX).   

73 David KC2WUF
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] More on RTTY RU signal report logging

[Jim Shorney]

I heard and worked one station running in RTTY RU mode tonight with RST 559
sent both ways.

Later I noteiced that the ADIF log file had 0 for both RST sent and RST rec,
while the Cabrillo file and all.txt have 559 both ways.

WSJT 2.0.0-rc2 compiled from the source tarball on the web site, Kubuntu 14.04
LTS 64 bit.

As a side note it looks like there is a still typo in crc.f90.

73

-Jim
NU0C

--
“There’s something out of place – let’s go and poke it with a stick.” – The 
Doctor, "Amy’s Choice"




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X V2.0 RC Contest Issues

[David Bean (KC2WUF) via wsjt-devel]

Joe et al,
I was running some RTTY RU contest tests tonight with some friends and noticed 
the following:
   
   - A friend was trying to answer CQ and people calling his CQ without any 
exchange entered in the correct text box and all transmits were <...> form. 
It would probably be advisable to notify anyone operating contest mode without 
an exchange (and if possible an invalid exchange) to get some type of warning.
   - I looked after a few contest QSOs and noticed that the Cabrillo file had 
the 5x9 received report, but had 59 for the sent report. It should be the 5x9 
that I sent.
   - The log QSO text box had no reports (5x9 sent/received) in it during the 
contest and therefore they weren't transferred into my logging program nor the 
ADI file. I did enter the 5x9 for both reports for one of the QSOs and it was 
sent along both chains (ADI and logging program via JT-AlertX).   

73 David KC2WUF
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.0.0-rc2 and JTAlertX Broken

[Thomas Webb]

CORRECTION: I was checking/unchecking the 'Show DX' in JTAlert.  Went back and 
unchecked 'Show DXCC
etc.' in WSJT-X ver 2.0/rc2; all functioning as advertised.  WSJT-X ver 1.9.1 
work fine with 'Show
DXCC' checked.

Tom WA9AFM/5 

-Original Message-
From: Thomas Webb [mailto:tmw...@cox.net] 
Sent: Tuesday, September 25, 2018 9:15 PM
To: 'WSJT software development'
Subject: Re: [wsjt-devel] WSJT-X 2.0.0-rc2 and JTAlertX Broken

Not getting response regardless if 'Show DX' is checked or not. Worked fine on 
rc1.

Tom, WA9AFM/5 

-Original Message-
From: Laurie, VK3AMA [mailto:_vk3a...@vkdxer.net]
Sent: Tuesday, September 25, 2018 5:01 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X 2.0.0-rc2 and JTAlertX Broken


On 26/09/2018 7:40 AM, Black Michael via wsjt-devel wrote:
> Yup...you're right...I don't run with that checked.
>
> de Mike W9MDB
Mike,

I too am seeing this behaviour. Something is broken in rc2 (I never tested rc1).
It is also affected the V3 Decodes History Beta which has been 100% reliable 
(that is I have not
received any advice to the contrary) in the Callsign click setup of WSJT-X.

de Laurie VK3AMA


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.0.0-rc2 and JTAlertX Broken

[Thomas Webb]

Not getting response regardless if 'Show DX' is checked or not. Worked fine on 
rc1.

Tom, WA9AFM/5 

-Original Message-
From: Laurie, VK3AMA [mailto:_vk3a...@vkdxer.net] 
Sent: Tuesday, September 25, 2018 5:01 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X 2.0.0-rc2 and JTAlertX Broken


On 26/09/2018 7:40 AM, Black Michael via wsjt-devel wrote:
> Yup...you're right...I don't run with that checked.
>
> de Mike W9MDB
Mike,

I too am seeing this behaviour. Something is broken in rc2 (I never tested rc1).
It is also affected the V3 Decodes History Beta which has been 100% reliable 
(that is I have not
received any advice to the contrary) in the Callsign click setup of WSJT-X.

de Laurie VK3AMA


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Band Activity window observations

[Dave Bernheisel via wsjt-devel]

Running 2.0.0-rc2 on Windows 10 Pro.

When I first started R2.0.0 I observed that the colors in the Band 
Activity window had changed.


When I changed the font color for LoTW, I thought I was selecting a font 
color for stations which


participate in LoTW as the button is labeled 'LoTW'.  I finally tumbled 
to the fact that the button means select the


font color for stations 'NOT LoTW'.

I use DXKeeper as my logging program.

I get some spots that are decoded and appear with a blue background.  
When I hover over the spot in JTAlertX (2.12.5) the only


criteria I see is that it is a 'Wanted Prefix'.  In fact, several of 
these decodes were for stations which are already in my DXKeeper log.


If I configure DXKeeper to track WPX in realtime, most of the needed 
prefix decodes go away.  But this flags the spots for these stations


in DXKeeper as wanted prefixes.  I don't want to chase prefixes. I have 
not found a place to deselect alerts for wanted prefixes, and it appears 
that the mechanism for detecting a wanted prefix is not working correctly.


The decoding and automation for working stations seems to work well.

Dave Bernheisel, N2DPF




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Blank lines

[Black Michael via wsjt-devel]

Ahh yes...that was it.  Thanks Laurie.I basically turned off all the colors and 
didn't notice the LOTW example blanked out too.

Mie
 

On Tuesday, September 25, 2018, 5:33:28 PM CDT, Laurie, VK3AMA 
<_vk3a...@vkdxer.net> wrote:  
 
 

On 26/09/2018 8:17 AM, Black Michael via wsjt-devel wrote:
> Anybody else seeing blank lines?  Happens on both windows.
> Screenshot included.
>
> de Mike W9MDB
Have you set the "LoTW" (should be called "Not LoTW" IMO) text color to 
white, so producing white text on white background? I was able to 
produce the blank line effect by doing that.

de Laurie VK3AMA



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Blank lines

[Laurie, VK3AMA]

On 26/09/2018 8:17 AM, Black Michael via wsjt-devel wrote:

Anybody else seeing blank lines?  Happens on both windows.
Screenshot included.

de Mike W9MDB
Have you set the "LoTW" (should be called "Not LoTW" IMO) text color to 
white, so producing white text on white background? I was able to 
produce the blank line effect by doing that.


de Laurie VK3AMA



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] 2.0.0-rc2 not decoding grid for EA1FA

[Ken Miller]

Using Win 10, 2.2.0-rc2 I5 quad core processor. It looks as EA1FA may be 
having trouble decoding. Sorry I did not have record sound file on at 
the time. I noticed this same thing yesterday and thought it was the 
mentioned HEX number/Call sign problem.


73 de k6wgx


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.0.0-rc2 and JTAlertX Broken

[Laurie, VK3AMA]

On 26/09/2018 7:40 AM, Black Michael via wsjt-devel wrote:

Yup...you're right...I don't run with that checked.

de Mike W9MDB

Mike,

I too am seeing this behaviour. Something is broken in rc2 (I never 
tested rc1).
It is also affected the V3 Decodes History Beta which has been 100% 
reliable (that is I have not received any advice to the contrary) in the 
Callsign click setup of WSJT-X.


de Laurie VK3AMA


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.0.0-rc2 and JTAlertX Broken

[Dan Malcolm]

Broken here in Win10

__
Dan – K4SHQ

From: Bill Barrett [mailto:w2pky...@gmail.com]
Sent: Tuesday, September 25, 2018 4:23 PM
To: Black Michael ; WSJT software development 

Subject: Re: [wsjt-devel] WSJT-X 2.0.0-rc2 and JTAlertX Broken

Hello Mike;
Seems to be an issue on Windows 7Pro.
Doubled checked  on several times.

Bill
W2PKY

On Tue, Sep 25, 2018 at 4:47 PM Black Michael via wsjt-devel 
mailto:wsjt-devel@lists.sourceforge.net>> 
wrote:
Nope...works fine here on WIndows 10.

de Mike W9MDB



On Tuesday, September 25, 2018, 3:34:14 PM CDT, Gene H 
mailto:ghin...@gmail.com>> wrote:


I have seen a problem with today's release of -rc2 whereby when I click
on a valid JTAlertX callsign the information is not being received and
processed by WSJT-X 2.0.0-rc2. Are others seeing the same problem? It
was working correctly on the -rc1 release. Also, I verified this is now
broken on two different Win7 computers and a friends station computer.
The JTAlertX version is 2.12.5.

Thanks for any feedback.

73 K5PA



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.0.0-rc2 and JTAlertX Broken

[Black Michael via wsjt-devel]

Yup...you're right...I don't run with that checked.
de Mike W9MDB


 

On Tuesday, September 25, 2018, 4:37:07 PM CDT, Tim Thorson 
 wrote:  
 
 Broke here, I checked the Show DXCC... box and it killed double-click/answer 
CQ action in JTAlert (v2.10.8).
Microsoft Windows 7 Home Premium
On Tue, Sep 25, 2018 at 2:25 PM Bill Barrett  wrote:

Hello Mike;Seems to be an issue on Windows 7Pro.Doubled checked  on several 
times.
BillW2PKY
On Tue, Sep 25, 2018 at 4:47 PM Black Michael via wsjt-devel 
 wrote:

Nope...works fine here on WIndows 10.
de Mike W9MDB


 
On Tuesday, September 25, 2018, 3:34:14 PM CDT, Gene H  
wrote:  
 
 I have seen a problem with today's release of -rc2 whereby when I click 
on a valid JTAlertX callsign the information is not being received and 
processed by WSJT-X 2.0.0-rc2. Are others seeing the same problem? It 
was working correctly on the -rc1 release. Also, I verified this is now 
broken on two different Win7 computers and a friends station computer. 
The JTAlertX version is 2.12.5.

Thanks for any feedback.

73 K5PA



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



-- 
Tim Thorson
916-572-3467 Amateur: KD6HOFGrid Square: 
CM98kv___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.0.0-rc2 and JTAlertX Broken

[Tim Thorson]

Broke here, I checked the Show DXCC... box and it killed
double-click/answer CQ action in JTAlert (v2.10.8).

Microsoft Windows 7 Home Premium

On Tue, Sep 25, 2018 at 2:25 PM Bill Barrett  wrote:

> Hello Mike;
> Seems to be an issue on Windows 7Pro.
> Doubled checked  on several times.
>
> Bill
> W2PKY
>
> On Tue, Sep 25, 2018 at 4:47 PM Black Michael via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
>> Nope...works fine here on WIndows 10.
>>
>> de Mike W9MDB
>>
>>
>>
>> On Tuesday, September 25, 2018, 3:34:14 PM CDT, Gene H 
>> wrote:
>>
>>
>> I have seen a problem with today's release of -rc2 whereby when I click
>> on a valid JTAlertX callsign the information is not being received and
>> processed by WSJT-X 2.0.0-rc2. Are others seeing the same problem? It
>> was working correctly on the -rc1 release. Also, I verified this is now
>> broken on two different Win7 computers and a friends station computer.
>> The JTAlertX version is 2.12.5.
>>
>> Thanks for any feedback.
>>
>> 73 K5PA
>>
>>
>>
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>


-- 
Tim Thorson
916-572-3467
Amateur: KD6HOF
Grid Square: CM98kv
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.0.0-rc2 and JTAlertX Broken

[Tim Thorson]

 Broke here, I checked the *Show DXCC*... box and it killed
double-click/answer CQ action in JTAlert (v2.10.8).

Microsoft Windows 7 Home Premium


On Tue, Sep 25, 2018 at 2:25 PM Bill Barrett  wrote:

> Hello Mike;
> Seems to be an issue on Windows 7Pro.
> Doubled checked  on several times.
>
> Bill
> W2PKY
>
> On Tue, Sep 25, 2018 at 4:47 PM Black Michael via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
>> Nope...works fine here on WIndows 10.
>>
>> de Mike W9MDB
>>
>>
>>
>> On Tuesday, September 25, 2018, 3:34:14 PM CDT, Gene H 
>> wrote:
>>
>>
>> I have seen a problem with today's release of -rc2 whereby when I click
>> on a valid JTAlertX callsign the information is not being received and
>> processed by WSJT-X 2.0.0-rc2. Are others seeing the same problem? It
>> was working correctly on the -rc1 release. Also, I verified this is now
>> broken on two different Win7 computers and a friends station computer.
>> The JTAlertX version is 2.12.5.
>>
>> Thanks for any feedback.
>>
>> 73 K5PA
>>
>>
>>
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.0.0-rc2 and JTAlertX Broken

[Bill Barrett]

Hello Mike;
Seems to be an issue on Windows 7Pro.
Doubled checked  on several times.

Bill
W2PKY

On Tue, Sep 25, 2018 at 4:47 PM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Nope...works fine here on WIndows 10.
>
> de Mike W9MDB
>
>
>
> On Tuesday, September 25, 2018, 3:34:14 PM CDT, Gene H 
> wrote:
>
>
> I have seen a problem with today's release of -rc2 whereby when I click
> on a valid JTAlertX callsign the information is not being received and
> processed by WSJT-X 2.0.0-rc2. Are others seeing the same problem? It
> was working correctly on the -rc1 release. Also, I verified this is now
> broken on two different Win7 computers and a friends station computer.
> The JTAlertX version is 2.12.5.
>
> Thanks for any feedback.
>
> 73 K5PA
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.0.0-rc2 and JTAlertX Broken

[Black Michael via wsjt-devel]

Nope...works fine here on WIndows 10.
de Mike W9MDB


 
On Tuesday, September 25, 2018, 3:34:14 PM CDT, Gene H  
wrote:  
 
 I have seen a problem with today's release of -rc2 whereby when I click 
on a valid JTAlertX callsign the information is not being received and 
processed by WSJT-X 2.0.0-rc2. Are others seeing the same problem? It 
was working correctly on the -rc1 release. Also, I verified this is now 
broken on two different Win7 computers and a friends station computer. 
The JTAlertX version is 2.12.5.

Thanks for any feedback.

73 K5PA



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.0.0-rc2 and JTAlertX Broken

[Bill Barrett]

Found in the new RC2 release on the General Tab if Show DXCC, grid, & WkB4
status is checked JTALertX can not start a contact by clicking a green box.
Sent this to Laurie as well.

Bill W2PK

On Tue, Sep 25, 2018 at 4:26 PM Gene H  wrote:

> I have seen a problem with today's release of -rc2 whereby when I click
> on a valid JTAlertX callsign the information is not being received and
> processed by WSJT-X 2.0.0-rc2. Are others seeing the same problem? It
> was working correctly on the -rc1 release. Also, I verified this is now
> broken on two different Win7 computers and a friends station computer.
> The JTAlertX version is 2.12.5.
>
> Thanks for any feedback.
>
> 73 K5PA
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc2

[Bill Barrett]

Joe:
Found in the new RC2 release on the General Tab if Show DXCC, grid, & WkB4
status is checked JTALertX can not start a contact by clicking a green box.
Sent this to Laurie as well.

Bill W2PKY

On Tue, Sep 25, 2018 at 12:22 PM Joe Taylor  wrote:

> A second candidate release of WSJT-X 2.0,  is now available for download
> and use by beta testers.  Changes in WSJT-X 2.0.0-rc2 relative to -rc1
> include the following:
>
>   - Corrected a flaw that encoded a message's first callsign as
> hexadecimal telemetry data if the call consisted only of letters
> A-F and digits 0-9.
>
>   - Corrected program logic that failed to identify certain callsigns
> as "nonstandard".
>
>   - Fixed a bug that color-highlighted bare CQ messages (no grid
> locator) as "New DXCC".
>
>   - Fixed a bug that failed to log Report Sent if MyCall is a
> nonstandard call.
>
>   - Fixed a bug that generated incorrect MSK144 tones for certain
> messages and caused a "memory" effect on stations receiving the
> incorrect tones.
>
>   - Fixed several bugs that could cause certain Tx messages to crash
> the program.
>
>   - Suppressed the display of certain illogical false decodes.
>
> The "Quick-Start Guide to WSJT-X 2.0" has been updated.  If you plan to
> use the beta-test release candidate, be sure to read this entire guide
> first:
> http://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf
>
>
> New features and enhancements in WSJT-X 2.0 relative to Version 1.9.1
> are summarized here:
>
> http://physics.princeton.edu/pulsar/k1jt/New_Features_WSJT-X_2.0.txt
>
> Download links for Windows, Linux, and macOS installation packages can
> be found on the WSJT-X web site
>
> http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
>
> We look forward to your feedback on WSJT-X 2.0-rc2.  Reports should be
> sent to the wsjt-devel email list, wsjt-devel@lists.sourceforge.net. You
> must subscribe to the list to post there.
>
> Reminder: A "mock contest" using FT8 mode and ARRL RTTY Roundup contest
> exchanges will be held tomorrow evening, NA time:
> Thursday, 27 September 0200-0259 UTC (Wednesday evening, NA time)
>
> A separate announcement about the mock contest will follow this one.
>
>  -- 73, Joe, K1JT (for the WSJT Development Group)
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X 2.0.0-rc2 and JTAlertX Broken

[Gene H]

I have seen a problem with today's release of -rc2 whereby when I click 
on a valid JTAlertX callsign the information is not being received and 
processed by WSJT-X 2.0.0-rc2. Are others seeing the same problem? It 
was working correctly on the -rc1 release. Also, I verified this is now 
broken on two different Win7 computers and a friends station computer. 
The JTAlertX version is 2.12.5.


Thanks for any feedback.

73 K5PA



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc2

[Joe Taylor]

Hi all,

The new bug that Jay found will also prevent proper auto-sequencing in 
MSK144 mode.  Those wishing to exercise the Version 2.0 MSK144 protocol 
are probably best advised to wait for us to fix this bug.


Sorry for the extra delay... we've been concentrating mostly on FT8 up 
to now.

-- Joe, K1JT

On 9/25/2018 3:31 PM, Joe Taylor wrote:

Hi Jay,

Thanks -- that's definitely a program defect, and we'll fix it.

In the meantime, when using MSK144 you'll need to enter DX Call manually 
and then type CTRL+L or click "Generate Std Msgs".


 -- 73, Joe, K1JT

On 9/25/2018 2:02 PM, Jay Hainline wrote:
Trying out the new RC2 release. In MSK144 mode, double clicking on a 
CQ call

in the Band Activity window to respond to a caller does not populate the
standard messages or turn on Enable TX. Works OK on FT8 mode. And 
responding

to a TX2 or TX4 message in msk144 mode works ok if double clicking on the
message. Only seems to be TX1 in msk144 where double clicking does not 
work.

This is on Windows 10 64 bit.

73 Jay KA9CFD

-Original Message-
From: Joe Taylor 
Sent: September 25, 2018 16:22
To: WSJT software development 
Subject: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc2

A second candidate release of WSJT-X 2.0,  is now available for 
download and
use by beta testers.  Changes in WSJT-X 2.0.0-rc2 relative to -rc1 
include

the following:

   - Corrected a flaw that encoded a message's first callsign as
 hexadecimal telemetry data if the call consisted only of letters
 A-F and digits 0-9.

   - Corrected program logic that failed to identify certain callsigns
 as "nonstandard".

   - Fixed a bug that color-highlighted bare CQ messages (no grid
 locator) as "New DXCC".

   - Fixed a bug that failed to log Report Sent if MyCall is a
 nonstandard call.

   - Fixed a bug that generated incorrect MSK144 tones for certain
 messages and caused a "memory" effect on stations receiving the
 incorrect tones.

   - Fixed several bugs that could cause certain Tx messages to crash
 the program.

   - Suppressed the display of certain illogical false decodes.

The "Quick-Start Guide to WSJT-X 2.0" has been updated.  If you plan 
to use

the beta-test release candidate, be sure to read this entire guide
first:
http://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf


New features and enhancements in WSJT-X 2.0 relative to Version 1.9.1 are
summarized here:

http://physics.princeton.edu/pulsar/k1jt/New_Features_WSJT-X_2.0.txt

Download links for Windows, Linux, and macOS installation packages can be
found on the WSJT-X web site

http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

We look forward to your feedback on WSJT-X 2.0-rc2.  Reports should be 
sent

to the wsjt-devel email list, wsjt-devel@lists.sourceforge.net. You must
subscribe to the list to post there.

Reminder: A "mock contest" using FT8 mode and ARRL RTTY Roundup contest
exchanges will be held tomorrow evening, NA time:
Thursday, 27 September 0200-0259 UTC (Wednesday evening, NA time)

A separate announcement about the mock contest will follow this one.

  -- 73, Joe, K1JT (for the WSJT Development Group)


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel





___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc2

[Joe Taylor]

Hi Jay,

Thanks -- that's definitely a program defect, and we'll fix it.

In the meantime, when using MSK144 you'll need to enter DX Call manually 
and then type CTRL+L or click "Generate Std Msgs".


-- 73, Joe, K1JT

On 9/25/2018 2:02 PM, Jay Hainline wrote:

Trying out the new RC2 release. In MSK144 mode, double clicking on a CQ call
in the Band Activity window to respond to a caller does not populate the
standard messages or turn on Enable TX. Works OK on FT8 mode. And responding
to a TX2 or TX4 message in msk144 mode works ok if double clicking on the
message. Only seems to be TX1 in msk144 where double clicking does not work.
This is on Windows 10 64 bit.

73 Jay KA9CFD

-Original Message-
From: Joe Taylor 
Sent: September 25, 2018 16:22
To: WSJT software development 
Subject: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc2

A second candidate release of WSJT-X 2.0,  is now available for download and
use by beta testers.  Changes in WSJT-X 2.0.0-rc2 relative to -rc1 include
the following:

   - Corrected a flaw that encoded a message's first callsign as
 hexadecimal telemetry data if the call consisted only of letters
 A-F and digits 0-9.

   - Corrected program logic that failed to identify certain callsigns
 as "nonstandard".

   - Fixed a bug that color-highlighted bare CQ messages (no grid
 locator) as "New DXCC".

   - Fixed a bug that failed to log Report Sent if MyCall is a
 nonstandard call.

   - Fixed a bug that generated incorrect MSK144 tones for certain
 messages and caused a "memory" effect on stations receiving the
 incorrect tones.

   - Fixed several bugs that could cause certain Tx messages to crash
 the program.

   - Suppressed the display of certain illogical false decodes.

The "Quick-Start Guide to WSJT-X 2.0" has been updated.  If you plan to use
the beta-test release candidate, be sure to read this entire guide
first:
http://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf


New features and enhancements in WSJT-X 2.0 relative to Version 1.9.1 are
summarized here:

http://physics.princeton.edu/pulsar/k1jt/New_Features_WSJT-X_2.0.txt

Download links for Windows, Linux, and macOS installation packages can be
found on the WSJT-X web site

http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

We look forward to your feedback on WSJT-X 2.0-rc2.  Reports should be sent
to the wsjt-devel email list, wsjt-devel@lists.sourceforge.net. You must
subscribe to the list to post there.

Reminder: A "mock contest" using FT8 mode and ARRL RTTY Roundup contest
exchanges will be held tomorrow evening, NA time:
Thursday, 27 September 0200-0259 UTC (Wednesday evening, NA time)

A separate announcement about the mock contest will follow this one.

  -- 73, Joe, K1JT (for the WSJT Development Group)


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel





___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] problem fixed

[Al Flapan]

Yes, it worked fine. Thanks Joe. Thanks Al for the contact to prove it.

Al  AF4FA

On 9/25/2018 2:46 PM, Al wrote:

( 2.0.0 RC2 )

Had a contact with AF4FA...   The hex problem seems to have been fixed.
Thanks
AL, K0VM


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] problem fixed

[Al]

( 2.0.0 RC2 )

Had a contact with AF4FA...   The hex problem seems to have been fixed.
Thanks
AL, K0VM
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc2

[Jay Hainline]

Trying out the new RC2 release. In MSK144 mode, double clicking on a CQ call
in the Band Activity window to respond to a caller does not populate the
standard messages or turn on Enable TX. Works OK on FT8 mode. And responding
to a TX2 or TX4 message in msk144 mode works ok if double clicking on the
message. Only seems to be TX1 in msk144 where double clicking does not work.
This is on Windows 10 64 bit.

73 Jay KA9CFD

-Original Message-
From: Joe Taylor  
Sent: September 25, 2018 16:22
To: WSJT software development 
Subject: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc2

A second candidate release of WSJT-X 2.0,  is now available for download and
use by beta testers.  Changes in WSJT-X 2.0.0-rc2 relative to -rc1 include
the following:

  - Corrected a flaw that encoded a message's first callsign as
hexadecimal telemetry data if the call consisted only of letters
A-F and digits 0-9.

  - Corrected program logic that failed to identify certain callsigns
as "nonstandard".

  - Fixed a bug that color-highlighted bare CQ messages (no grid
locator) as "New DXCC".

  - Fixed a bug that failed to log Report Sent if MyCall is a
nonstandard call.

  - Fixed a bug that generated incorrect MSK144 tones for certain
messages and caused a "memory" effect on stations receiving the
incorrect tones.

  - Fixed several bugs that could cause certain Tx messages to crash
the program.

  - Suppressed the display of certain illogical false decodes.

The "Quick-Start Guide to WSJT-X 2.0" has been updated.  If you plan to use
the beta-test release candidate, be sure to read this entire guide
first:
http://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf


New features and enhancements in WSJT-X 2.0 relative to Version 1.9.1 are
summarized here:

http://physics.princeton.edu/pulsar/k1jt/New_Features_WSJT-X_2.0.txt

Download links for Windows, Linux, and macOS installation packages can be
found on the WSJT-X web site

http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

We look forward to your feedback on WSJT-X 2.0-rc2.  Reports should be sent
to the wsjt-devel email list, wsjt-devel@lists.sourceforge.net. You must
subscribe to the list to post there.

Reminder: A "mock contest" using FT8 mode and ARRL RTTY Roundup contest
exchanges will be held tomorrow evening, NA time:
Thursday, 27 September 0200-0259 UTC (Wednesday evening, NA time)

A separate announcement about the mock contest will follow this one.

 -- 73, Joe, K1JT (for the WSJT Development Group)


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel





___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Decode Background Colors - Suggestions

[Mike]

I was trying to change the colors in WSJT-X v 2.0.0 rc2 to the way I had
some of them in the previous versions when I realized I don't understand
the logic or priority of them.

Let's just take one situation as an example. Suppose a call is decoded that
is a [new call] & [new grid] at the same time - what default color does the
program display - blue or orange? Of course you can have a new call that is
not a new grid and vice-versa. But what happens if both logic conditions
apply (or even more than two)?

Also, some operators like me may not want the New Grid or New Grid on Band
colors to operate at all (or perhaps more than those two). I see no way to
disable any of the colors. Changing the background color to white doesn't
disable them though, it just uses white as the color. So then the white
color still competes with other logic conditions and other colors as above.

You can pick other examples as well. What is the logic for the colors when
multiple conditions arise for the same call sign? Can the program please
include an option such as check boxes to actually disable the particular
decode alert color, not simply change it's color?

Thanks,
Mike - N5INP
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] RTTY RU mode questions

[Joe Taylor]

Hi Don,

On 9/25/2018 10:03 AM, Don AA5AU wrote:
I have some questions in trying to set up for tomorrow night's FT8 
Roundup test.


1. Will the QSO get logged automatically to the Cabrillo file or will I 
have to manually log it? Typically is use JTAlert to log into DXKeeper 
but I don't think I want to do that for a contest. It seems the QSO 
should be logged automatically.


When any one of the contest-like activities has been selected, completed 
QSOs are logged to both "wsjtx_log.adi" and "cabrillo.log" when you 
click "OK" on the Log QSO window.


Your other questions are answered in the Reminder announcement about the 
mock contest.


-- Joe, K1JT


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Reminder: Mock "FT8 Roundup" Contest

[Joe Taylor]

A one-hour "practice contest" will be held tomorrow (Wednesday evening, 
NA time) using the FT8 mode and the ARRL RTTY Roundup rules.


Date and time: Thursday, 27 September 0200-0259 UTC

Dial frequencies 7.078 and 14.078, everyone works everyone.

To participate you must use WSJT-X 2.0, either -rc1 or -rc2.
Installation packages for Windows, Linux, and macOS can be found on the 
bottom of this web page:

https://physics.princeton.edu/pulsar/k1jt/wsjtx.html

The Quick-Start Guide to WSJT-X 2.0 is posted here:
https://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf

OPERATING ADVICE FOR THE MOCK CONTEST:

1. On the *Settings | Advanced* tab, be sure to check the boxes *Always 
generate 77-bit messages*, *Decode only 77-bit messages*, and *ARRL RTTY 
Roundup*.  In the field labeled "Exch" enter the 2- or 3-letter 
abbreviation for your state or province (US/Canadian stations) or DX if 
you are not in the US or Canada.


2. Be sure that 7.078 and 14.078 appear in your drop-down frequency list 
for FT8 mode.  You might need to do a *Reset* on the *Settings | 
Frequencies* tab.


3. We do not recommend using a compound or nonstandard callsign in this 
event.


4. To keep track of stations already worked in the contest, you will 
probably want to start with an empty wsjtx_log.adi file.  I suggest 
invoking the command *File | Open log directory*.  Then right-click on 
the file "wsjtx_log.adi" and rename it to something else, for example 
"wsjtx_log.bak".  After the mock contest be sure to reverse this 
procedure to restore your working ADIF log.


5. Before the mock contest starts, execute the command *File | Erase 
cabrillo.log*.


Please post your results and comments here so we can all learn from an 
FT8 contest-like experience. Note that planning is underway for at least 
two dedicated FT8 contests to be potentially held in the next few 
months. This practice run will help to inform those plans.


-- 73, Joe, K1JT


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Candidate release WSJT-X 2.0.0-rc2

[Joe Taylor]

A second candidate release of WSJT-X 2.0,  is now available for download 
and use by beta testers.  Changes in WSJT-X 2.0.0-rc2 relative to -rc1 
include the following:


 - Corrected a flaw that encoded a message's first callsign as
   hexadecimal telemetry data if the call consisted only of letters
   A-F and digits 0-9.

 - Corrected program logic that failed to identify certain callsigns
   as "nonstandard".

 - Fixed a bug that color-highlighted bare CQ messages (no grid
   locator) as "New DXCC".

 - Fixed a bug that failed to log Report Sent if MyCall is a
   nonstandard call.

 - Fixed a bug that generated incorrect MSK144 tones for certain
   messages and caused a "memory" effect on stations receiving the
   incorrect tones.

 - Fixed several bugs that could cause certain Tx messages to crash
   the program.

 - Suppressed the display of certain illogical false decodes.

The "Quick-Start Guide to WSJT-X 2.0" has been updated.  If you plan to 
use the beta-test release candidate, be sure to read this entire guide 
first:

http://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf


New features and enhancements in WSJT-X 2.0 relative to Version 1.9.1 
are summarized here:


http://physics.princeton.edu/pulsar/k1jt/New_Features_WSJT-X_2.0.txt

Download links for Windows, Linux, and macOS installation packages can 
be found on the WSJT-X web site


http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

We look forward to your feedback on WSJT-X 2.0-rc2.  Reports should be 
sent to the wsjt-devel email list, wsjt-devel@lists.sourceforge.net. You 
must subscribe to the list to post there.


Reminder: A "mock contest" using FT8 mode and ARRL RTTY Roundup contest 
exchanges will be held tomorrow evening, NA time:

Thursday, 27 September 0200-0259 UTC (Wednesday evening, NA time)

A separate announcement about the mock contest will follow this one.

-- 73, Joe, K1JT (for the WSJT Development Group)


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X rc2.01

[Al Pawlowski]

So far, no problems seen using both regular and 77bit FT8 modes with standard 
call sign. Tried some MSK144 on 6m - looked good, but have not had any return 
calls.

May be my imagination, but the WSJT-X output signal seems to provide better 
modulation (less sideband and amplitude jitter). Decode ability may be a bit 
better - I seem to be seeing more -22 and -24.


Al Pawlowski, K6AVP
Los Osos, CA USA





___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] RTTY RU mode questions

[Don AA5AU]

I have some questions in trying to set up for tomorrow night's FT8 Roundup test.
1. Will the QSO get logged automatically to the Cabrillo file or will I have to 
manually log it? Typically is use JTAlert to log into DXKeeper but I don't 
think I want to do that for a contest. It seems the QSO should be logged 
automatically.
2. If the QSO is logged automatically, is there any indication the QSO has been 
logged to the Cabrillo file?
3. I don't see a color set up for stations already worked on a band. How do you 
know if a station is a dupe... because it's not colored coded at all? 
4. Should wsjt_log.adi be cleared before the contest? Is that the file that 
determines how calls are color coded?

Thanks,
Don AA5AU___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] (no subject)

[James Shaver]

Can someone please block this user?  This is the 5th blank note from this 
person. 

> On Sep 25, 2018, at 6:25 AM, Анатолий  wrote:
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Bug: WSJT-X 2.0 only recognizes 4-digit grid squares but not 6-digit grid squares

[DG2YCB, Uwe]

Meanwhile I made some more tests. It is indeed the case that WSJT-X
2.0.0-rc1 recognizes from the file wsjt_log.adi only 4-digit grid squares,
but NOT 6-DIGIT GRID SQUARES! Please be so kind as to fix this bug asap.

 

When I change in the wsjt_log.adi file generated from my standard logbook
manually the an entry like KM46ck to KM46 then
the station is correctly shown as worked B4. For the GRIDSQUARE:6 entry it
is always shown as "New Grid". This is the reason why I have so many New
Grid  false positives.

 

73 de Uwe, DG2YCB 

 

Von: DG2YCB, Uwe [mailto:dg2...@gmx.de] 
Gesendet: Montag, 24. September 2018 08:59
An: wsjt-devel@lists.sourceforge.net
Betreff: [wsjt-devel] New Grid false positives

 

Hi,

 

Using WSJT-X v2.0.0-rc1 I am still having lots false positives regarding New
Grids. As there was no helpful answer to my previous post so far, and
assuming that WSJT-X is taking information about worked callsigns, grids, et
cetera from the file wsjt_log.adi, just made the following test: Created a
new wsjt_log.adi with all QSO entries from my standard logbook and saved
into AppData/local/WSJT-X directory. Result: WSJT-X 1.9.1 works with it
without any mistake regarding recognition of B4 stations, but WSJT-X
2.0.0-rc1 now SHOWS EVERY STATION AS A NEW GRID.  Same file in the same
directory. Checked as examples SV5DKL, VP8LP  and ER1PB. They are in my
wsjt_log.adi with following entries:

 20170910 085300 SV5DKL 17m
18.1 FT8 KM46ck Dodecanese
Efstathios Maliakis 2 -8 Rhodes
085500 

20171230 090400 VP8LP 17m
18.1 FT8 GD18bh Falkland Islands
Bob Mcleod 0 -11 Stanley
090500 

20180726 144900 ER1PB 12m
24.915 FT8 KN47KA Moldova
Simanenkov Sergei -4 -11 Chisinau
145100 

"New Grids" were exactly the grids which are in the adif file (in WSJT-X
2.0.0-rc1 of course as 4-digit grids). 

Is there a bug in WSJT-X v2.0.0-rc1 recognizing 6-digit grid squares from
wsjt_log.adi file?

73 de Uwe, DG2YCB 

 

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] (no subject)

[Анатолий]

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Use of sourceforge.net

[Bill Somerville]

On 25/09/2018 06:32, Claude Frantz wrote:

In my opinion, releases candidates should be available in the git repo.


Hi Claude,

the current situation is that we have reset the way we do development 
and at present we are meeting the requirements of the GPLv3 licence, 
that WSJT-X is protected by, by releasing a source tarball alongside 
public releases. This tarball is in fact sanitized and although it 
includes all sources necessary to build the release it does not contain 
all the sources used by the developers to do R and other internal 
design and discussion documents. Related to this is the full change 
history that fully describes all the steps made to the source control 
repository, if we pushed the repository to SourceForge then the full 
history and current state of all documents would be included, which we 
will not continue to do. It is our intention to do such a push of the 
development repository, but the filtering of some working documents is 
not trivial and will involve an extra burden on the development team, 
this is being worked on.


Bottom line is that we would like to do all development in public but 
having suffered misuse of such openness we could only continue with the 
current team if this was addressed. I fully agree that testing by 
enthusiastic users like yourself is an excellent way to improve the 
application and to catch many defects early but *for now* public 
availability of sources is limited to release candidates and full 
General Availability (GA) releases. this is no different from many Open 
Source projects, including those that were "knocking-off" the WSJT-X 
sources before we have deemed them ready for general release, and the 
alternative would have been the exit of one or more key development 
contributors which I am sure no one would be happy with.


73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel