Here's the patch to fix the double-click on <...>
de Mike W9MDB
*** "..\\wsjtx-2.1.0\\src\\wsjtx\\decodedtext.cpp" 2019-02-24
21:48:37.000000000 -0600--- decodedtext.cpp 2019-09-06 11:59:42.921762600
-0500****************** 10,16 ****
namespace {! QRegularExpression words_re
{R"(^(?:(?<word1>(?:CQ|DE|QRZ)(?:\s?DX|\s(?:[A-Z]{2}|\d{3}))|[A-Z0-9/]+)\s)(?:(?<word2>[A-Z0-9/]+)(?:\s(?<word3>[-+A-Z0-9]+)(?:\s(?<word4>(?:OOO|(?!RR73)[A-R]{2}[0-9]{2})))?)?)?)"};
}
DecodedText::DecodedText (QString const& the_string)--- 10,16 ----
namespace {! QRegularExpression words_re
{R"(^(?:(?<word1>(?:CQ|DE|QRZ)(?:\s?DX|\s(?:[A-Z]{2}|\d{3}))|[\<\.\<A-Z0-9/]+)\s)(?:(?<word2>[A-Z0-9/]+)(?:\s(?<word3>[-+A-Z0-9]+)(?:\s(?<word4>(?:OOO|(?!RR73)[A-R]{2}[0-9]{2})))?)?)?)"};
}
DecodedText::DecodedText (QString const& the_string)
On Wednesday, September 4, 2019, 05:22:29 PM CDT, Star Light
<[email protected]> wrote:
Yeah, agree. That’s pretty much it. And in my case (still coming up the
learning curve), there’s time wasted making sure I didn’t do something wrong,
didn’t accidentally miss-set a setting somewhere, aren’t trying to do something
that’s actually not appropriate or allowed, and by the time I get down that
logic tree and start what Mike described, it’s pretty much too late. Yeah Joe,
sorry - it’s frustrating.
However, it doesn’t happen very often (to me) and I sure don’t mean to make a
big deal out of it. I just wanted to contribute to the frequency-of-report
statistics to be helpful. If you guys don’t hear about things, how can you
know about them? Sorry if reporting frustration annoyed you.
On Sep 4, 2019, at 7:18 AM, Black Michael via wsjt-devel
<[email protected]> wrote:
Let me give an example
Running JTAlert (I don't even look at the WJST-X window anymore) you see a call
you want...you click on it...and nothing happens. Then JTAlert clears the
screen for the next decode (especially in FT4) and if you're not lucky enough
to remember the callsign have to go to WSJT-X, stop the monitoring, find the
entry that you missed (again remembering the callsign), double-click on it (for
those that don't know that it doesn't work), then type in the callsign to the
DX box, enable monitoring again.
I call that frustrating IMHO.
de Mike W9MDB
On Wednesday, September 4, 2019, 08:57:51 AM CDT, Joe Taylor
<[email protected]> wrote:
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
_______________________________________________
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
