I seem to be having a bad day. I upgraded from 2.3.0 to 2.5.4. I have never
downloaded or installed 2.5.0.
So my revised report is:
I updated from WSJT-X ver 2.3.0 to ver 2.5.4 both Win 64 bit and I noticed the
following changes. I used the term regressions in the title because I think
On 27.1.2022 17.14, Andy Durbin via wsjt-devel wrote:
I updated from WSJT-X ver 2.3.0 to ver 2.5.0
Umm... The latest release is 2.5.4. Perhaps try that one.
73's de Kari, oh2gqc
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
Hello Team-
Running 2.5.2 "deep decode" recently saw 90-100 decodes posted on 40M in
the evening but the waterfall and JTAlert show about 1/2.
Finally the Band Activity section shows about 1/2 the large count. Anyone
else seeing this?
Thanks;
Bill W2PKY
On Thu, Jan 27, 2022 at 11:53 AM Andy
I updated from WSJT-X ver 2.3.0 to ver 2.5.0 both Win 64 bit and I noticed the
following changes. I used the term regressions in the title because I think
they are. The developers may not agree that this characterization is correct.
1. Main window size is no longer remembered through a
re - Interaction with JTAlert has changed for single clicked callsigns. In
2.3.0 any decoded call would move the RX frequency cursor and populate the
Received frequency pane with the decode. In 2.5.0 only a subset of decoded
calls is responsive. (See HamApps thread "No click response if CQ
