Re: [wsjt-devel] Bug in 2.5.1?

2021-10-23 Thread Lance Collister, W7GJ via wsjt-devel
Hi Charlie, I think the problem was operator fatigue - VY SRI! I did experience last night the same thing that you did. The problem I was encountering I guess was difficulty finding the exact same sequence to reply to again when I returned to calling a previous station, and wanted to

Re: [wsjt-devel] Bug in 2.5.1?

2021-10-23 Thread Joe Taylor via wsjt-devel
Hi Lance, I cannot confirm the behavior you describe. As far as I can see, double-clicking on an average decode appearing in the Average Decodes window behaves just as it did before, and as intended. -- 73, Joe, K1JT On 10/23/2021 8:44 AM, Lance Collister, W7GJ via wsjt-devel

Re: [wsjt-devel] Bug in 2.5.1?

2021-10-23 Thread Charles Suckling via wsjt-devel
Hi Lance I'm not seeing that here with 2.5.1. I tested replying to a CQ call and clicking on an average decode (there were no single period decodes in my benchmark test files) it populates the messages correctly with the S/N of the decoded average message. 73 Charlie On Sat, 23 Oct 2021 at

[wsjt-devel] Bug in 2.5.1?

2021-10-23 Thread Lance Collister, W7GJ via wsjt-devel
I finally was able to download 2.5.1, even though I am not using compound callsign at the moment. One thing I noticed that seems to be different is that when I click on a decode in the AVERAGE window to reply, the program used to reply with the signal strength shown in the decode. Now that