HI Paul,
thanks for that clarification, we too are finding this issue hard to
reproduce so be patient, we will sort it out eventually.
73
Bill
G4WJS.
On 14/05/2020 4:09, Paul Kube wrote:
Hi Bill,
Yes this is with v2.2.0-rc1, Win 10 64 bit.
As I recall, it only occurred when there was just one late decode, and
no decodes in the following period. It happened several times in quick
succession, but I failed to get a screenshot or any more clues; and I
haven't seen it again. I apologize for such a sketchy bug report. I'll
try to reproduce it and let you know.
Meanwhile, thanks for all your hard work on this. I'm liking this new
release a lot.
73, Paul K6PO
On Tue, May 12, 2020 at 6:11 PM Bill Somerville <g4...@classdesign.com
<mailto:g4...@classdesign.com>> wrote:
On 13/05/2020 02:01, Paul Kube wrote:
On Tue, May 12, 2020 at 1:29 PM Bill Somerville
<g4...@classdesign.com <mailto:g4...@classdesign.com>> wrote:
Most users will see ... more decodes overall with the last
few maybe only printing some time into the following period.
On this point: When a signal is sent in a period, but decoded in
the next period, I have seen the transmission appear with the
"wrong" timestamp in the Band Activity pane.
73, Paul K6PO
Paul,
are you observing this behaviour in WSJT-X v2.2.0 RC1, or in a
prior version?
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
