Mike,
Of course LOL!! This is the second time in as many weeks I have been caught
shooting my mouth off about something that got fixed one version ago from where
I am at.
Thank you for the correction!!
73 de Bill ND0B
From: Black Michael [mailto:mdblac...@yahoo.com]
Sent: Monday, January 2, 2017 11:41 AM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
It was removed in 7442
de Mike W9MDB
_____
From: Bill ND0B <n...@ockert.us <mailto:n...@ockert.us> >
To: 'WSJT software development' <wsjt-devel@lists.sourceforge.net
<mailto:wsjt-devel@lists.sourceforge.net> >
Sent: Monday, January 2, 2017 11:17 AM
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
Good morning,
I just noticed this morning using r7441 that TX Enable is disabled (and the log
prompt pops up) at the start of a TX4 transmission. This is new behavior in
one of the recent versions and I agree with those asserting it appears to be in
error. The contact can be considered over when one of the stations RECEIVES
RRR, not when one of the stations transmits it.
Enable Tx and Halt Tx appear to operate as they always have, this is a change
in how “Disable TX after sending 73” is interpreted. I do not believe it to
be correct to interpret this as disabling TX after sending an RRR. This does
not make sense either semantically or operationally.
73 de Bill ND0B
From: ANDY DURBIN [mailto:a.dur...@msn.com]
Sent: Monday, January 2, 2017 8:54 AM
To: wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
"I figured out my issue with the auto sequencing stopping at RRR. It does not
have anything to do with with prompt to log pop up. I had Disable TX after
sending 73 checkmarked in Settings/General tab. For some reason, it is
disabling TX after sending RRR instead."
You have been caught by what I think is a very misleading user interface!
In earlier versions of wsjt-x if "Enable TX" was not red you could not
transmit. The name was consistent with the behaviour.
The function was then changed to enable auto sequencing (or something
similar). Now the Enable TX light extinguishes at the start of 73 but the 73
continues to be sent.
I don't know why this behaviour was changed but I don't like it. The current
interface is misleading because several items were not changed to reflect the
new behaviour.
1. The button is still called "Enable TX" but TX is still enabled when it is
not lit
2. The behaviour option is called "Disable TX after sending 73" but this
selection actually disables auto sequencing at start of 73
3. The tool tip for the behaviour option does not describe what the option
actually does
4. The tool tip for the Enable Tx button does not describe what the
button/light does/indicates.
Either the behaviour needs to be changed back to how it used to be or the
function names need to match what the system actually does. My preference
would be to go back to it being an Enable TX function. If the Enable Tx
button really did what is was labeled as, there would be no need for the Halt
TX button.
73,
Andy k3wyc
_____
From: wsjt-devel-requ...@lists.sourceforge.net
<mailto:wsjt-devel-requ...@lists.sourceforge.net>
<wsjt-devel-requ...@lists.sourceforge.net
<mailto:wsjt-devel-requ...@lists.sourceforge.net> >
Sent: Monday, January 2, 2017 6:53 AM
To: wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
Subject: wsjt-devel Digest, Vol 35, Issue 9
Send wsjt-devel mailing list submissions to
wsjt-devel@lists.sourceforge.net
<mailto:wsjt-devel@lists.sourceforge.net>
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
<https://lists.sourceforge.net/lists/listinfo/wsjt-devel> wsjt-devel Info Page
- SourceForge
lists.sourceforge.net
Your email address: Your name (optional): You may enter a privacy password
below. This provides only mild security, but should prevent others from messing
with ...
or, via email, send a message with subject or body 'help' to
wsjt-devel-requ...@lists.sourceforge.net
<mailto:wsjt-devel-requ...@lists.sourceforge.net>
You can reach the person managing the list at
wsjt-devel-ow...@lists.sourceforge.net
<mailto:wsjt-devel-ow...@lists.sourceforge.net>
When replying, please edit your Subject line so it is more specific
than "Re: Contents of wsjt-devel digest..."
Today's Topics:
1. Re: Prompt to log QSO when either RRR or 73 is sent (Jay Hainline)
2. Re: Prompt to log QSO when either RRR or 73 is sent
(Bill Somerville)
----------------------------------------------------------------------
Message: 1
Date: Mon, 2 Jan 2017 13:40:47 -0000
From: "Jay Hainline" <ka9...@mtcnow.net <mailto:ka9...@mtcnow.net> >
Subject: Re: [wsjt-devel] Prompt to log QSO when either RRR or 73 is
sent
To: "'WSJT software development'" <wsjt-devel@lists.sourceforge.net
<mailto:wsjt-devel@lists.sourceforge.net> >
Message-ID: <004801d264fd$d3a2c8d0$7ae85a70$@mtcnow.net
<mailto:004801d264fd$d3a2c8d0$7ae85a70$@mtcnow.net> >
Content-Type: text/plain; charset="utf-8"
I figured out my issue with the auto sequencing stopping at RRR. It does not
have anything to do with with prompt to log pop up. I had Disable TX after
sending 73 checkmarked in Settings/General tab. For some reason, it is
disabling TX after sending RRR instead.
73 Jay KA9CFD
From: Jay Hainline [mailto:ka9...@mtcnow.net]
Sent: January 1, 2017 22:08
To: 'Black Michael' <mdblac...@yahoo.com <mailto:mdblac...@yahoo.com> >; 'WSJT
software development' <wsjt-devel@lists.sourceforge.net
<mailto:wsjt-devel@lists.sourceforge.net> >
Subject: RE: [wsjt-devel] Prompt to log QSO when either RRR or 73 is sent
I don?t know for certain why this was changed in the first place except the
JT65 HF crowd is always looking for a way to sidestep a sequence to shorten the
time for a QSO. This does not work in the meteor scatter VHF world where you
are relying on random data bits to fly in on a meteor for less than 1 second
and you are trying to decode just what the guy on the other end has received.
If it aint broke, don?t fix it.
I hope I don?t get black balled for being negative like the Ham Radio Deluxe
people do to users of their software. Lol ;-)
73 Jay KA9CFD
From: Black Michael [ <mailto:mdblac...@yahoo.com> mailto:mdblac...@yahoo.com]
Sent: Sunday, January 1, 2017 3:39 PM
To: WSJT software development < <mailto:wsjt-devel@lists.sourceforge.net>
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> >
Subject: Re: [wsjt-devel] Prompt to log QSO when either RRR or 73 is sent
I think the consensus solution would be to make it a user option.
Seems the meteor scatter people have the most problems with it since they were
quick to speak up.
I had proposed at one time to make the "Prompt me to log QSO" a tri-state box
so one could check 73, 73+RRR, or none. But seems the binary choice is clearer
and there are no other tri-state checkboxes in WSJT-X.
So this patch makes it optional with an added option line below the current
prompt option. All worlds should be happy with this.
<https://www.dropbox.com/s/s5xwpc39bubmzxx/rrr_option.patch?dl=1>
https://www.dropbox.com/s/s5xwpc39bubmzxx/rrr_option.patch?dl=1
de Mike W9MDB
_____
From: Seb < <mailto:w...@miamisky.com> w...@miamisky.com
<mailto:w...@miamisky.com> >
To: WSJT software development < <mailto:wsjt-devel@lists.sourceforge.net>
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> >
Sent: Sunday, January 1, 2017 1:26 PM
Subject: Re: [wsjt-devel] Prompt to log QSO when either RRR or 73 is sent
IMHO the introduction of the log QSO prompt when you are sending RRR does not
solve or help anything.
It is useless when you are doing meteor scatter. If I?m sending Tx3 and the
other station hears that and sends Tx4 and then logs the contact, it is not a
valid QSO because I have no idea if the other station has heard my report. I
will end up sending Tx3 several times until I just give up on the contact.
73 de Sebastian, W4AS
On Jan 1, 2017, at 9:38 AM, Jay Hainline < <mailto:ka9...@mtcnow.net>
ka9...@mtcnow.net <mailto:ka9...@mtcnow.net> > wrote:
This was introduced in r7431. I think its bad form to get a prompt to log the
QSO when you are sending RRR. How do you know if your QSO partner has received
it if he does not send 73 back to you??
Jay Hainline KA9CFD
Colchester, IL EN40om
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! <http://sdm.link/slashdot>
http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
<mailto:wsjt-devel@lists.sourceforge.net> wsjt-devel@lists.sourceforge.net
<mailto:wsjt-devel@lists.sourceforge.net>
<https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Mon, 2 Jan 2017 13:53:41 +0000
From: Bill Somerville <g4...@classdesign.com <mailto:g4...@classdesign.com> >
Subject: Re: [wsjt-devel] Prompt to log QSO when either RRR or 73 is
sent
To: wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
Message-ID: <88cd7f71-519d-d86e-abcd-b04edce31...@classdesign.com
<mailto:88cd7f71-519d-d86e-abcd-b04edce31...@classdesign.com> >
Content-Type: text/plain; charset="windows-1252"
On 02/01/2017 13:40, Jay Hainline wrote:
> I figured out my issue with the auto sequencing stopping at RRR. It
> does not have anything to do with with prompt to log pop up. I had
> Disable TX after sending 73 checkmarked in Settings/General tab. For
> some reason, it is disabling TX after sending RRR instead.
Hi Jay,
the disabling of auto Tx and the automatic pop up of the logging dialog
are currenty linked. I believe the thinking was that if you are able to
log then you should stop sending. IMHO this is only true for the caller
as the station running the frequency is obliged to keep sending RRR
until they are sure that the caller has seen it, even though their end
of the QSO is compete and they can log it. This made sense when the
logging reminder only came up for 73 messages, now it also does for RRR
messages and that is causing the problem here.
Maybe we should pop up the log QSO dialog but only disable auto Tx once
the Ok has been clicked. Another option might be to split the setting
into two options like "Prompt to Log QSO" and "Disable auto Tx *after*
logging", the latter maybe only applying if the message that prompted
logging was a 73 message.
There must be a way of doing this that satisfies all modes and operating
methods.
73 & HNY
Bill
G4WJS.
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------------------------------------------------------
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
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
End of wsjt-devel Digest, Vol 35, Issue 9
*****************************************
------------------------------------------------------------------------------
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
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
