Re: [wsjt-devel] WSJT-X RX Window not in chronological order

2019-02-26 Thread Frank Kirschner
I think you just noticed it. I've been seeing that since version 1.9. I use Windows 7. I never thought much about it, looking at several lines to figure out which one was the last one sent. 73, Frank KF6E On Tue, Feb 26, 2019, 13:18 Bill wrote: > I recently upgraded to version 2.0.1 and notic

Re: [wsjt-devel] WSJT-X RX Window not in chronological order

2019-02-26 Thread Bill
Thanks for the response Frank. I guess its possible that I never noticed it but I sure can't remember seeing it before. I have almost 10K FT8 QSOs and today is the first time that has jumped out at me. I always focus on that the last line of the RX window. The really weird thing is that the ALL.TXT

Re: [wsjt-devel] WSJT-X RX Window not in chronological order

2019-02-26 Thread Joe Taylor
Bill -- On 2/26/2019 1:18 PM, Bill AK6A wrote: I recently upgraded to version 2.0.1 and noticed an issue I haven't seen before. It appears that the entries in the RX window are not always in chronological order with the intermixed TX lines. There have been no changes here. Text lines have a

Re: [wsjt-devel] WSJT-X RX Window not in chronological order

2019-02-26 Thread George J Molnar
I’ve noticed this in situations where there are more decodes than can be processed in between TX/RX cycles. Solution is to improve computer performance, change to a quieter frequency, or constrain your decode bandwidth a bit. George J Molnar KF2T - Virginia, USA > _

Re: [wsjt-devel] WSJT-X RX Window not in chronological order

2019-02-26 Thread WB5JJJ
I concur as this has been an ongoing issue for some time. They RX window is not properly sorted which can lead to confusion. On Tue, Feb 26, 2019 at 12:45 PM Bill wrote: > Thanks for the response Frank. I guess its possible that I never noticed > it but I sure can't remember seeing it before. I

Re: [wsjt-devel] WSJT-X RX Window not in chronological order

2019-02-26 Thread Bill
Thanks Joe. Yes, this was observed using FT8. Its just strange that I never noticed this before. It was on 20m with a completely full band so that might have been the issue. The bands are a lot more crowded than they used to be so that might be why I'm noticing it now. I'm running a 4Ghz i7 iMac so