Hi Mike
I use sequence
CQ HF1D
HF1D DK1XX JO43
DK1XX HF1D -09
HF1D DK1XX R-03
And finally
RR TU 73LOTW
HF1D DK1XX 73
Best regards, 73
Jerry, HF1D
From: Игорь Ч [mailto:[email protected]]
Sent: Friday, December 11, 2015 2:52 PM
To: WSJT software development <[email protected]>
Subject: Re: [wsjt-devel] RR73 message button
Hi Mike,
That is exactly what happens: after the RRR message most users consider as
polite way to send the 73 mesage.
Alternative option could be R73.
73 Igor
Re: [wsjt-devel] RR73 message button
From: Michael Black < <mailto:mdblack98@gm...> mdblack98@gm...> - 2015-12-11
13:23:54
Attachments: Message as HTML
We've gone through this discussion before...I used to think it was a good
idea too. But...RR73 is a grid location...and RRR is the last message for
the CQ side of the QSO...not 73.
So you don't save any time by doing RR73 unless you would otherwise do an
RRR followed by an unnecessary 73.
It's just hard to drop the habit of using 73 like you use on every other
protocol.
RRR :-)
Mike W9MDB
Пятница, 11 декабря 2015, 12:15 +03:00 от Игорь Ч <c <mailto:[email protected]>
[email protected]>:
Hi Joe and all,
I have checked statistics based on the All.txt file: at least every second
operator transmit manually generated message RR73 or 'RRR 73' instead of the
standard RRR message. File with the summary and raw data in MS Excel format is
located there: <https://cloud.mail.ru/public/4KBg/UoqJWw6rK>
https://cloud.mail.ru/public/4KBg/UoqJWw6rK
Summary does not include scenario where some operators use 73 message instead
of the RRR one.
There are three reasons to modify user interface with this message:
1. It should reduce spectrum usage and interference on the overcrowded HF bands
2. It will make GUI more user friendly one
3. It will save time, both, in terms of the QSO length and manual message
generation
Also possibility to activate prompt for QSO logging on the RR73 message would
benefit users.
May I ask to consider the code change in some future release, please?
73 Igor UA3DJY
------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
