There are peoples "hunting" and other "working QSO's en masse".
Dennis want to go to CQ just after QSO.
FT8 do what he needs. He works like "QSO>CQ>QSO>CQ etc.
Of course FT8 made it possible.
I do not negate this kind of work.
I don't ask to kick-out CQ from FT8.
I ask to make another path to
I think everyone here is slightly confused...
Henryk,
Two things need to be checked in WSJT-X settings. On the General Tab
in Settings, check the following two items:
"Double Click on Call sets TX enable", and, "Disable Tx after sending 73"
What these two setting do for you is after you
: Wednesday, July 13, 2022 12:35 PM
To: WSJT software development
Cc: Henryk Majcher
Subject: Re: [wsjt-devel] Unwanted CQ in FT8
Hi Neil
You completely didn't understand what I asked.
The frame "TX 7" should be empty. It is a stand by position.
No transmit, when it is checked.
Res
Hi Neil
You completely didn't understand what I asked.
The frame "TX 7" should be empty. It is a stand by position.
No transmit, when it is checked.
Resume: "TX 7" is not a macro.
Henryk SP3E
śr., 13 lip 2022 o 14:28 Neil Zampella via wsjt-devel <
wsjt-devel@lists.sourceforge.net> napisał(a):
That can be done using the 'Free Text' area and macros from JT
Alert. No need to add another standard message. As far as
'unwanted' CQs, uncheck the CALL 1ST checkbox.
Neil, KN3ILZ
On 7/12/2022 7:31 PM, Henryk Majcher wrote:
I propose a small change in WSJT-X.
Scenario:
The users of
I propose a small change in WSJT-X.
Scenario:
The users of WSJT-X are
* CQ fans
* Hunters (Squares, DXCC, Zones)
Actually after QSO (even incomplete) the circle left of TX6 is checked
and WSJT-X is ready to send CQ.
It is super nice for CQ fans.
What WSJT-X offers for Hunters? Nothing
I
