Good morning Steve,
I was bitching about this “feature” this morning and Hasan let me know he had
brought this up with the developers in the past and was told it was the
expected behavior. Please allow me to weigh in on this issue with a few
points:
1. I concur that WSJTx currently stays in the last sequence it was in when
Generate Standard Messages is clicked. Several points on this:
a. This is a recent change in behavior as prior WSJTx went to TX1 on
Generate Standard Messages. I am still in the habit of expecting this.
b. This was an option in WSJT. I believe it was eliminated as an option
and made to always happen in x because nearly everyone who knew about the
option checked it. I certainly did.
c. This is inconsistent and thus unexpected behavior as double clicking a
call forces a Generate Standard Messages
AND TX1
2. It “might” make sense to continue calling CQ if TX6 was the last
message. More often than not it is not the operators intent. More on this
later.
3. It makes absolutely no sense if the previous state was something other
than TX1 or TX6, it would be rare and unusual circumstances that would have the
QSO starting with the most likely previous state, TX4 or TX5.
4. If it is the operators intent to start on a different sequence they can
just as easily move from TX1 as any other to the desired sequence.
5. At a minimum this should be an option like it was in WSJT.
More on the second point. I am from North Dakota and one of very few folks
from here who are both on the WSJTx modes and on LOTW. On a couple of bands I
am the only one on both of these from the state. I have lost count, it has to
be in the hundreds, of the stations who completed WAS by working me. What I
am not is much of a fan of HF, I hang out on 6, 2 and 222 meteor scatter and
only go to HF when asked which happens several times a month. If the station
that has asked me for a sked starts out calling CQ they have just wasted my
time and I go back to meteor scatter and do not respond to further emails from
that station. As HF is not where I operate it is of little concern to me
that the program, not the operator, acted unexpectedly. For some of these
stations it is of great consequence.
73 de Bill ND0B
From: Steven Franke [mailto:[email protected]]
Sent: Tuesday, September 12, 2017 8:49 PM
To: Joe Taylor <[email protected]>
Subject: Re: [wsjt-devel] Dx Call Entry with Gnerate Std Msgs Should Default to
TX6 (CQ)
Hi Hasan,
The behavior that I observe is: populate the DX Call box, click Generate Std
Msgs box, and the TX1 thru TX6 boxes are populated. The Tx state remains
wherever it was when this sequence of steps was initiated. If I Generate Std
Msgs with the Tx1 box checked, then the Tx1 box remains checked after the
messages are generated. I don’t see the problem. Surely it should be up to the
operator to determine which state to start in.
Further, it is surely reasonable that one side of a prearranged sked might want
to populate the DX Call box and then call CQ. As you know, skeds sometimes
proceed this way - two stations meet on a frequency with a prior understanding
that, say, “A” would answer “B’s” CQ, if possible.
Steve k9an
On Sep 12, 2017, at 9:22 PM, Hasan al-Basri <[email protected]
<mailto:[email protected]> > wrote:
I have played with this quite a bit and cannot figure out the reason for the
following:
I meet a station on Ping Jockey and we agree to begin a qso. I enter his call
in the blank DX Call box , K1SIX. I click the Generate Std Msgs box, and the
TX1 thru TX6 populate.
But...the TX defaults to TX6...CQ...that makes no sense to me.
Any time someone bothers to Generate Std Messages, it seems to me that the next
operation is most certainly going to be TX1...I can think of no circumstance
after hitting Gen Std Msgs that I would be calling CQ.
Is it possible that any time GEn Std Msgs is clicked, the default operation
could be set to TX1 ?
Please excuse me if I'm missing something obvious, maybe I'm just blinded by my
own operational style.
TIA, 73 N0AN
Hasan
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org <http://slashdot.org> !
http://sdm.link/slashdot_______________________________________________
wsjt-devel mailing list
[email protected] <mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
