Joe,
"Of course you're welcome to use good-old-r3673 as long as you like. But you'll
then do without three years worth of very significant program enhancements and
improvements "
Yes, of course I understand that. I only referenced r3673 to show that what
Bill stated was untrue. 3 years ago is not "never". The decoder enhancements
have made it advantageous to use 1.7.0 even for HF.
73,
Andy k3wyc
________________________________
From: wsjt-devel-requ...@lists.sourceforge.net
<wsjt-devel-requ...@lists.sourceforge.net>
Sent: Monday, January 2, 2017 10:22 AM
To: wsjt-devel@lists.sourceforge.net
Subject: wsjt-devel Digest, Vol 35, Issue 12
Send wsjt-devel mailing list submissions to
wsjt-devel@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
wsjt-devel Info Page -
SourceForge<https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
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
You can reach the person managing the list at
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: Disable Tx after RRR/73 (Bill Somerville)
2. MSK144 Timing Flag? (George J Molnar)
3. Re: Disable Tx after RRR/73 (Joe Taylor)
4. Re: Disable Tx after RRR/73 (Black Michael)
5. Re: Disable Tx after RRR/73 (ANDY DURBIN)
----------------------------------------------------------------------
Message: 1
Date: Mon, 2 Jan 2017 16:55:43 +0000
From: Bill Somerville <g4...@classdesign.com>
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
To: wsjt-devel@lists.sourceforge.net
Message-ID: <2126fb3b-c133-ab79-c532-81ace5650...@classdesign.com>
Content-Type: text/plain; charset="windows-1252"
On 02/01/2017 16:50, Black Michael wrote:
> I think it's a case of semantics. If you push "Tx" button on rig it
> starts Tx...."Enable Tx" sounds a lot like that.
>
> "Enable Tx Next" might be more appropos. Even then if you Enable
> during a Tx period it starts but at least that still meets the "Next"
> behavior I think. Or "Tx Allowed".
Hi Mike,
that is a bit rich given all the comments about reducing the UI width!
One could also argue that the button caption should be "Tx" so as not to
contribute to the UI minimum width. Maybe it should be changed to a
check box option which has semantics of "Tick now to affect things
later" rather than the push button semantic of "Do it now".
73
Bill
G4WJS.
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Mon, 2 Jan 2017 09:02:05 -0800
From: George J Molnar <geo...@molnar.com>
Subject: [wsjt-devel] MSK144 Timing Flag?
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Message-ID: <65141be4-659b-4264-87d1-256d9b1ca...@molnar.com>
Content-Type: text/plain; charset="utf-8"
Is there room in the MSK144 protocol to include a ?duration? flag, indicating
the sequence length selected by the transmitting station? In meteor scatter
use, length isn?t usually obvious by listening, and mismatched sequence times
could create undesired interference and longer times to complete.
I would suspect that MSK144 short sequences will find use during Es season,
too. Having the software able to match sequences would be handy.
73/HNY
George J Molnar
Nevada, USA
KF2T @GJMolnar
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 3
Date: Mon, 2 Jan 2017 12:06:01 -0500
From: Joe Taylor <j...@princeton.edu>
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Message-ID: <205166bd-1ed2-4a4f-3b8d-9fd0f0d12...@princeton.edu>
Content-Type: text/plain; charset=windows-1252; format=flowed
Andy --
K3WYC wrote:
> That assertion is simply not true. I keep v1.3 r3673 on my computer so I
> can check things like this. In r3673 pressing the lit "Enable Tx" button
> while transmitting a message does stop the message transmission!
WSJT-X v1.3 (r3673) was made more than three years ago. At that time
the program was simple: it offered two modes, JT9 and JT65, and it was
useful only at HF.
WSJT-X Version 1.7 offers nine modes and is used from LF and MF through
24 GHz. Yes, some user-interface behavior has evolved over time. But
the program is still nearly 100% compatible with older versions, even
for users who still use only the original supported modes. When we make
behavioral changes we generally have good reasons for doing so.
The WSJT-X User Guide makes it very clear what "Enable Tx" means, and
what it does:
"Enable Tx toggles automatic T/R sequencing mode on or off and
highlights the button in red when ON. A transmission will start at the
beginning of the selected (odd or even) sequence, or immediately if
appropriate. Toggling the button to OFF during a transmission allows the
current transmission to finish."
Of course you're welcome to use good-old-r3673 as long as you like. But
you'll then do without three years worth of very significant program
enhancements and improvements -- even if you never use anything but JT9
and JT65.
-- Joe, K1JT
------------------------------
Message: 4
Date: Mon, 2 Jan 2017 17:17:36 +0000 (UTC)
From: Black Michael <mdblac...@yahoo.com>
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Message-ID: <14132813.5364129.1483377456...@mail.yahoo.com>
Content-Type: text/plain; charset="utf-8"
Maybe it should be Yellow when enabled and not transmitting?Red when
transmitting?? A bit like the status line?
Just throwing out ideas for consideration.? I think those of us who have been
operating this for a while may not be able to perceive the new user experience.
de Mike W9MDB
From: Bill Somerville <g4...@classdesign.com>
To: wsjt-devel@lists.sourceforge.net
Sent: Monday, January 2, 2017 10:55 AM
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
On 02/01/2017 16:50, Black Michael wrote:
I think it's a case of semantics.? If you push "Tx" button on rig it starts
Tx...."Enable Tx" sounds a lot like that.
"Enable Tx Next" might be more appropos.? Even then if you Enable during a Tx
period it starts but at least that still meets the "Next" behavior I think.? Or
"Tx Allowed".
Hi Mike, that is a bit rich given all the comments about reducing the UI
width! One could also argue that the button caption should be "Tx" so as not to
contribute to the UI minimum width. Maybe it should be changed to a check box
option which has semantics of "Tick now to affect things later" rather than the
push button semantic of "Do it now".
73
Bill
G4WJS.
------------------------------------------------------------------------------
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
wsjt-devel Info Page -
SourceForge<https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
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 ...
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 5
Date: Mon, 2 Jan 2017 17:22:32 +0000
From: ANDY DURBIN <a.dur...@msn.com>
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
To: "wsjt-devel@lists.sourceforge.net"
<wsjt-devel@lists.sourceforge.net>
Message-ID:
<by1pr16mb013512b7bcac07bc4a9c83c38c...@by1pr16mb0135.namprd16.prod.outlook.com>
Content-Type: text/plain; charset="iso-8859-1"
"so are you saying that you want to revert to having no "Halt Tx"
button and have the "Enable Tx" button have two functions that cannot be
separated?"
There was always a Halt TX button but, with the r3673 functionality of Enable
TX, I don't think it was needed. Removing it would not be reversion.
The first step would be to understand why the change from "TX Enable" to "Next
Enable" was made. I see no advantage but I only use JT9 and JT65 on HF and 6m.
I assume there was some advantage in other operating environments.
If the arguments for the change are still valid then, obviously, it won't be
changed back to the simple TX Enable that it used to be in r3673 and earlier.
If that is the case then I hope the description inconsistencies that I listed
earlier will be addressed.
Moving to brainstorming mode - The color red seems inappropriate for the
indicator for either functionality. If tri-state is an option I'd suggest no
fill for no TX possible (no change), Green for auto enable - this message and
the next one will be sent, and Amber for this message is the last one that will
be sent. Colors would change at the end of the TX period or when this button
or Halt TX was pressed.
73,
Andy k3wyc
________________________________
From: wsjt-devel-requ...@lists.sourceforge.net
<wsjt-devel-requ...@lists.sourceforge.net>
Sent: Monday, January 2, 2017 9:50 AM
To: wsjt-devel@lists.sourceforge.net
Subject: wsjt-devel Digest, Vol 35, Issue 11
Send wsjt-devel mailing list submissions to
wsjt-devel@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
wsjt-devel Info Page -
SourceForge<https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
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 ...
wsjt-devel Info Page -
SourceForge<https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
wsjt-devel Info Page -
SourceForge<https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
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 ...
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
You can reach the person managing the list at
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: Disable Tx after RRR/73 (Bill Somerville)
2. Re: Disable Tx after RRR/73 (ANDY DURBIN)
3. Re: Disable Tx after RRR/73 (Bill Somerville)
4. Re: Disable Tx after RRR/73 (Black Michael)
----------------------------------------------------------------------
Message: 1
Date: Mon, 2 Jan 2017 15:07:33 +0000
From: Bill Somerville <g4...@classdesign.com>
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
To: wsjt-devel@lists.sourceforge.net
Message-ID: <eb5e6493-1280-d049-33cb-8417fdb16...@classdesign.com>
Content-Type: text/plain; charset="windows-1252"
On 02/01/2017 14:54, ANDY DURBIN wrote:
> My preference would be to go back to it being an Enable TX function.
Hi Andy,
the "Enable Tx" button has always been "Enable auto Tx", in fact the
underlying variable name is autoButton and it always has been.
Because the message protocols restrict you to transmitting in only the
first or second period of the sequence the only interpretation of that
button is transmit when it is next possible to do so. That may be now or
at the start of the next suitable period. The "Halt Tx" button is not
the antithesis of "Enable Tx" but it does happen to toggle it off, this
is because it makes sense to not transmit again after a request to "Halt
Tx". Once a transmission is started the "Halt Tx" button is the way to
stop it, toggling "Enable Tx" to off does not do that, it never has.
73
Bill
G4WJS.
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Mon, 2 Jan 2017 16:40:20 +0000
From: ANDY DURBIN <a.dur...@msn.com>
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
To: "wsjt-devel@lists.sourceforge.net"
<wsjt-devel@lists.sourceforge.net>
Message-ID:
<by1pr16mb0135fc13afce12de27de67048c...@by1pr16mb0135.namprd16.prod.outlook.com>
Content-Type: text/plain; charset="iso-8859-1"
"Once a transmission is started the "Halt Tx" button is the way to stop it,
toggling "Enable Tx" to off does not do that, it never has."
Bill,
That assertion is simply not true. I keep v1.3 r3673 on my computer so I can
check things like this. In r3673 pressing the lit "Enable Tx" button while
transmitting a message does stop the message transmission!
"Enable TX" used to be just that - Enable TX - and if it was not lit then no TX
was possible.
73,
Andy k3wyc
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 3
Date: Mon, 2 Jan 2017 16:43:38 +0000
From: Bill Somerville <g4...@classdesign.com>
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
To: wsjt-devel@lists.sourceforge.net
Message-ID: <7bddb2fe-42c4-1562-5818-82b407da1...@classdesign.com>
Content-Type: text/plain; charset="windows-1252"
On 02/01/2017 16:40, ANDY DURBIN wrote:
>
> That assertion is simply not true. I keep v1.3 r3673 on my computer so
> I can check things like this. In r3673 pressing the lit "Enable Tx"
> button while transmitting a message does stop the message transmission!
>
> "Enable TX" used to be just that - Enable TX - and if it was not lit
> then no TX was possible.
>
Hi Andy,
ok, so are you saying that you want to revert to having no "Halt Tx"
button and have the "Enable Tx" button have two functions that cannot be
separated?
73
Bill
G4WJS.
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 4
Date: Mon, 2 Jan 2017 16:50:10 +0000 (UTC)
From: Black Michael <mdblac...@yahoo.com>
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Message-ID: <1938249038.5348081.1483375810...@mail.yahoo.com>
Content-Type: text/plain; charset="utf-8"
I think it's a case of semantics.? If you push "Tx" button on rig it starts
Tx...."Enable Tx" sounds a lot like that.
"Enable Tx Next" might be more appropos.? Even then if you Enable during a Tx
period it starts but at least that still meets the "Next" behavior I think.? Or
"Tx Allowed".
de Mike W9MDB
From: Bill Somerville <g4...@classdesign.com>
To: wsjt-devel@lists.sourceforge.net
Sent: Monday, January 2, 2017 10:43 AM
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
On 02/01/2017 16:40, ANDY DURBIN wrote:
That assertion is simply not true. I keep v1.3 r3673 on my computer so I can
check things like this. In r3673 pressing the lit "Enable Tx" button while
transmitting a message does stop the message transmission! "Enable TX" used to
be just that - Enable TX - and if it was not lit then no TX was possible.
Hi Andy, ok, so are you saying that you want to revert to having no "Halt Tx"
button and have the "Enable Tx" button have two functions that cannot be
separated? 73
Bill
G4WJS.
------------------------------------------------------------------------------
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
wsjt-devel Info Page -
SourceForge<https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
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 ...
wsjt-devel Info Page -
SourceForge<https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
wsjt-devel Info Page -
SourceForge<https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
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 ...
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 ...
-------------- 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
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
wsjt-devel Info Page -
SourceForge<https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
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 ...
wsjt-devel Info Page -
SourceForge<https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
wsjt-devel Info Page -
SourceForge<https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
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 ...
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 ...
End of wsjt-devel Digest, Vol 35, Issue 11
******************************************
-------------- 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
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
wsjt-devel Info Page -
SourceForge<https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
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 ...
End of wsjt-devel Digest, Vol 35, Issue 12
******************************************
------------------------------------------------------------------------------
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
