Forgot to mention, these were for normal type callsigns.
> On Nov 1, 2018, at 09:30, wsjt-devel-requ...@lists.sourceforge.net wrote: > > From: Al Pawlowski <k6...@almont.com> > To: WSJT software development <wsjt-devel@lists.sourceforge.net> > Subject: Re: [wsjt-devel] wsjt-devel Digest, Vol 57, Issue 1 > Message-ID: <e44550df-4329-4eff-a13b-32e64df1d...@almont.com> > Content-Type: text/plain; charset="utf-8" > > Similar (rc3 on Win) problem just occurred with me. Using Tab 1 messages, had > ?CQ DX? set in the ?free? message selection. Double clicked a return caller?s > line in Rx Freq pane. The message stayed on the ?free? message and continued > to transmit the ?CQ DX? even though I tried double clicking on him in Band > activity pane and on his JTAlert bubble. Return caller?s callsign also did > not enter in the message or DX call boxes. Had to ?halt? the tx, input the > return caller?s callsign in Dx Call, generate messages, click message 2 and > enable Tx to get the proper response going - unfortunately, not in time to > get the QSO. > > I have also had a few times (with band pretty busy) that the program did not > auto answer/respond to a correctly decoded return-after-cq, but did then > start auto-sequencing correctly after double clicking on the return call. > > Appears there is an auto sequence problem associated with the ?free? message > that did not seem to be in previous versions and, maybe, when the decoder is > really busy. > > Al Pawlowski, K6AVP > Los Osos, CA USA _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
