Hi Andy, Mike, Russ, ...

Yes, double-clicking on the decoded message "<...> 9M2TO -18" does not copy 9M2TO into the DX Call entry box. Yes, we should probably add this capability some time.

Frustrating??? Really, I don't get it. How hard can it be to type "9M2TO" into the DX Call box, and then click on "Generate Std Msgs" ??

As you probably noticed, most recent programming effort has been devoted to smooth operation of FT4/FT8 in the contesting environment.

        -- Joe, K1JT

On 9/3/2019 5:02 PM, Star Light wrote:
Had this same problem yesterday as well (different station).  Very frustrating...

Russ, KR6W


On Sep 3, 2019, at 9:09 AM, Black Michael via wsjt-devel <[email protected] <mailto:[email protected]>> wrote:

This has been asked numerous times and I've never seen a reply about it.
I'd like to think it has been fixed but nobody knows what changes are done anymore.

de Mike W9MDB




On Tuesday, September 3, 2019, 11:06:35 AM CDT, Andy Durbin <[email protected] <mailto:[email protected]>> wrote:


With WSJT-X 2.1.0 and this group of decodes displayed in "Band activity" :

135600  -3  0.2  991 ~  CQ KD5FOY EM12
135600 -16  0.6 2207 ~  AE4CC N4HAI -04
------------------------------------ 30m
135615 -14  0.1 2240 ~  <...> 9M2TO -18     <<
------------------------------------ 30m
135630  -8  0.2  990 ~  CQ KD5FOY EM12
135630 -18  0.1 1638 ~  CQ KB8SRX EN82
------------------------------------ 30m
135700  -8  0.2  991 ~  CQ KD5FOY EM12
135700 -12  0.6 2207 ~  AE4CC N4HAI -04

Double click on 9M2TO gives no response but double click on any other decode line moves that decode to "RX Frequency", moves the RX cursor, and generates appropriate messages.   Why is 9M2TO unresponsive? The transmitting stations call, frequency, and signal report are known.  A knowledge of who 9M2TO was in QSO with should not be needed since CQ calls are moved to "RX Frequency".

Is lack of response to a double click on 9M2TO decode intended operation?

In this case 9M2TO was also unresponsive in JTAlertX.

73,
Andy, k3wyc
_______________________________________________
wsjt-devel mailing list
[email protected] <mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected] <mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to