Re: [wsjt-devel] Program crashes

[Joe T. <jo...@pr...>]

OK Morris, thanks for reporting this new defect.  It seems to apply to 
any message with two callsigns followed by 73.  We'll fix it.

	-- Joe, K1JT

On 8/30/2017 8:50 PM, Morris Wideman wrote:
> Hi Joe
> There should have been a screen shot of the call in the software and 
> here is the wave file it decoded but still could double click and insert 
> call.
> I will be leaving home no radio for few days but should have email 
> access but not my radio computer or such.
> Thanks Morris WA4MIT
> 
> 
> On Wednesday, August 30, 2017, 7:23:28 PM CDT, Joe Taylor 
> <jo...@pr...> wrote:
> 
> 
> On 8/30/2017 6:14 PM, Morris Wideman via wsjt-devel wrote:
> 
>  > I was not able to make WSJT-X development release 8049 pick up this
>  > callsign "K4XP" a legitimate US callsign and transfer it to DX Call by
>  > double click. I was trying to pick up a new state for FT8 on 15M after
>  > he had worked another station. This always works and worked today on
>  > other callsigns but not K4XP. I tried several times just would not pick
>  > it up.
>  > 73 WA4MIT
> 
> 
> You haven't included a relevant .wav file or line of decoded text, so
> it's impossible to diagnose your problem with confidence.
> 
> My best guess is that you received the callsign K4XP as part of
> something WSJT-X would consider a "free text" message.
> 
> For example, double-clicking on this decoded text line will not work
> 
> 000001 -15  0.0 1500 ~  CQ VT WY K4XP
> 
> ... because "CQ VT WY K4XP" is not a legal structured message in any of
> the "JT" protocols.
> 
>      -- 73, Joe, K1JT
>