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 does
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 15:
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 wrote:
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 maintai
Hi Lance
Yes, I understand. But, I'm not sure there is a benefit in you keeping the
report the same for a previous caller if another QSO intervenes.
Consider the situation from the caller's perspective. They start a QSO off
with you and get their first report. If that does not decode, it will
Lance, W7GJ wrote:
...Maybe if there were an option to keep the signal report the
same even if there are a number of intervening contacts or transmissions to
other stations, I guess that is what I am trying to do by hand and failing
miserably at... Do you understand my dilemma?
MNI TN
That was the way it always was in EME before Q65...everybody was OOO. I
still wish there were some option for that and for an initial CALL3.TXT
lookup so I could see who was calling me on what frequency. I have been
guessing like mad typing in various callsigns into the DX STATION
callsign box