Joe,
Thank you for your response, sorry to have wasted your time.
Comments inserted below.
73 de Bill ND0B
-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: Monday, January 2, 2017 1:57 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Ideas for Develop
On 1/2/2017 1:33 PM, Gordon Higgins wrote:
> What is the meaning of the tail nombers in msk155
> ie g3pxt dk9wi +01 1 8 -0.8
The first number is described in the WSJT-X User Guide, in a table found
here:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-1.7.0.html#_decoded_l
On 02/01/2017 19:54, Black Michael wrote:
Here it is with the radius zeroed.
The radius did look a bit strange just being on the bottom.
Hi Mike,
that rather misses the point. The non-customized native windows control
(somewhat version dependent) for a progress bar doesn't have radii at
the
Hi Bill (ND0B) and all,
I've been away most of the time since your post, and just now finding
time to respond. You gave us a long list of ideas, with no evident
prioritization. You mentioned to me that you were "in the process of
learning C++ and QT by immersion". Of course you're the best j
Here it is with the radius zeroed.The radius did look a bit strange just being
on the bottom.
https://www.dropbox.com/s/q7t70yxdvrouyms/progressbar2.patch?dl=1
de Mike W9MDB
From: Bill Somerville
To: wsjt-devel@lists.sourceforge.net
Sent: Monday, January 2, 2017 1:38 PM
Subject: Re:
Bill,
I don't see the "mangled" in the Mac version. Are you referring to no radius
on the top of the widget? Looks the same on Windows.
de Mike W9MDB
From: Bill Somerville
To: wsjt-devel@lists.sourceforge.net
Sent: Monday, January 2, 2017 1:38 PM
Subject: Re: [wsjt-devel] Disable
On 02/01/2017 18:15, Bill Somerville wrote:
Not just the images but the public functions, nothing to change
color. Thanks for the correction, much appreciated,,
HI Bill,
you can certainly change the rendering of any Qt widget either by
using a sytle sheet or delegate if supported or a cus
Just lurking here ...
However, I do not feel it is a good idea to mess with the button. I
seem to remember that at one time, before v1.6 at least the ENABLE
button could be used to stop transmission. However, that was also
somewhat confusing since there was a HALT TX button there too.
Reminder to all:
This reflector is here to facilitate communication among WSJT
developers. We would prefer to keep it open to everyone interested, at
least on a "mostly SWL" basis. But it's counterproductive for the list
to require volumes of developer responses to user wishes.
Of course, su
Hi Joe,
Figured I would ask before I went off on a tangent again.
What are your plans for CQ AA through CQ ZZ?That seems a reasonable
range for what I am proposing to indicate sequence length, SH status and
contest mode.
Thanks!
73 de Bill ND0B
---
"a better tool tip is definitely ok, any suggestions? The button caption is a
bit more tricky as longer will probably make the UI wider."
Suggestions only and not a demand for anything -
1. Change button text from "Enable Tx" to "Auto TX". It's more accurate and
shorter.
2. Change button to
This works on Windows using a stylesheet. You got a Mac you could test? At
worst I'd think it would ignore it.
Does red on tx, green on rx.Puts the ratio in the bar rather than next to
it.Adds a little rounding to the bottom corners.Gets rid of the flashing
behavior.
https://www.dropbox.com/
What is the meaning of the tail nombers in msk155
ie g3pxt dk9wi +01 1 8 -0.8
On 2 January 2017 at 18:24, Bill ND0B wrote:
> Bill,
>
>
>
> Got it. I know where to look now for the exact how of what I want to
> do.
>
>
>
> Much appreciated!
>
>
>
> 73 de Bi
Bill,
Got it. I know where to look now for the exact how of what I want to do.
Much appreciated!
73 de Bill ND0B
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Monday, January 2, 2017 12:20 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] MSK144 T
On 02/01/2017 17:57, Bill ND0B wrote:
I suspected something like this but am still looking into it / getting
up to speed.This was why I specifically suggest this apply only to
the CQ message as being the shortest, it might, take on something like
this and did coach it with “if it will fit”
On 02/01/2017 18:09, ANDY DURBIN wrote:
" You are trying to force your view of usage which seems unreasonable
given there is a valid alternative."
I'm not trying to force anything. The user interface is misleading
because of the nomenclature that is used on the button, in the option,
and
On 02/01/2017 18:05, Bill ND0B wrote:
Not just the images but the public functions, nothing to change color.
Thanks for the correction, much appreciated,,
HI Bill,
you can certainly change the rendering of any Qt widget either by using
a sytle sheet or delegate if supported or a custom pa
" You are trying to force your view of usage which seems unreasonable given
there is a valid alternative."
I'm not trying to force anything. The user interface is misleading because of
the nomenclature that is used on the button, in the option, and in the tool
tips. The functionality is c
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Monday, January 2, 2017 12:00 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
On 02/01/2017 17:55, Bill ND0B wrote:
Even just color?
Hi Bill,
Yes I'm afraid so. See the images here fo
On 02/01/2017 17:55, Bill ND0B wrote:
Even just color?
Hi Bill,
Yes I'm afraid so. See the images here for examples:
http://doc.qt.io/qt-5/qprogressbar.html#details
73
Bill
G4WJS.
--
Check out the vibrant tech comm
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Monday, January 2, 2017 11:47 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] MSK144 Timing Flag?
On 02/01/2017 17:12, Bill ND0B wrote:
I posted a few things I am working on a couple of days ago. This is one
Even just color?
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Monday, January 2, 2017 11:51 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
On 02/01/2017 17:47, Black Michael wrote:
I kinda' like that ideathat flashing bar shoul
Mike,
I am kind of the “red” means transmit school. That seems to show up a lot of
places other than WSJT.
While it is “wicked awesome” and someone probably spent some time figuring out
how to do it I find the flashing aspect of it a bit annoying too.
Maybe a less redder red? On
On 02/01/2017 17:47, Black Michael wrote:
I kinda' like that ideathat flashing bar should have more
meaningit's really a bit annoying but giving it some more meaning
would make it more tolerable.
But should it go red or yellow? I can see it either way. Yellow
matches all the other T
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
I kinda' like that ideathat flashing bar should have more meaningit's
really a bit annoying but giving it some more meaning would make it more
tolerable.
But should it go red or yellow? I can see it either way. Yellow matches all
the other Tx indicators...but red says "hey dude...you'r
On 02/01/2017 17:12, Bill ND0B wrote:
I posted a few things I am working on a couple of days ago. This is
one of them and I believe there is room for a single character in the
CQ message to indicate this and a few other operational items. Here
were my comments on what I propose to develop…
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: Mo
It was removed in 7442
de Mike W9MDB
From: Bill ND0B
To: 'WSJT software development'
Sent: Monday, January 2, 2017 11:17 AM
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
#yiv0617045516 #yiv0617045516 -- _filtered #yiv0617045516 {panose-1:2 4 5 3 5 4
6 3 2 4;} _filtered #yiv06
Or alternately the progress bar for the current sequence could be colored red
or green depending on “progress” of TX or RX respectively.
73 de Bill ND0B
From: Black Michael [mailto:mdblac...@yahoo.com]
Sent: Monday, January 2, 2017 11:36 AM
To: WSJT software development
Subject: Re: [
Hi Andy,
comments in line below.
On 02/01/2017 17:22, ANDY DURBIN wrote:
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 internal implementation is an auto transmit enable, having it al
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
That Green/Yellow makes sense to me...that coloring matches the rx/tx mode and
the colors on the Rx Frequency list plus the status line. All would show green
on Rx and yellow on Tx.
The main advantage in the red is that it does stand out letting you know you
will be transmitting which is an imp
Good morning George,
I posted a few things I am working on a couple of days ago. This is one of
them and I believe there is room for a single character in the CQ message to
indicate this and a few other operational items. Here were my comments on
what I propose to develop…
> 8.
"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 reversi
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
Fro
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
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
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
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 Mi
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
"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 whil
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 yo
"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
Hello Bill. I did not uncheck "Auto Seq". Just the "Disable TX after sending
73" box in the Settings. I still have "Prompt me to log QSO" checkmarked but
the program does not stop TX after sending RRR now. It continues on to TX5
sending the 73 message. I have to click on the "Enable TX" button to m
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
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: Ja
47 matches
Mail list logo
