On 04/01/2017 16:07, Black Michael wrote:
> Are you amenable to introducing an #ifndef Q_OS_DARWIN around it so we
> can leave Mac users to their druthers?
Hi Mike,
as I demonstrated above, the same applies to MS Windows with its shaded
and animated standard progress bar which is rendered at a
Sent: Wednesday, January 4, 2017 9:50 AM
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
On 04/01/2017 15:25, Black Michael wrote:
I minimized the style sheet to just set color. Can you see what this looks
like on Mac? Does it still completely change the appearance? Are you trying to
ma
On 04/01/2017 15:25, Black Michael wrote:
I minimized the style sheet to just set color.
Can you see what this looks like on Mac? Does it still completely
change the appearance?
Are you trying to maintain the "look and feel" for Mac and not apply a
style sheet for that reason?
I minimized the style sheet to just set color.Can you see what this looks like
on Mac? Does it still completely change the appearance?Are you trying to
maintain the "look and feel" for Mac and not apply a style sheet for that
reason?
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
uary 2, 2017 1:38 PM
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
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
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
ving way too far from that behaviour IMHO.
73
Bill
G4WJS.
------ next part --
An HTML attachment was scrubbed...
--
Message: 2
Date: Mon, 2 Jan 2017 17:41:10 + (UTC)
From: Black Michael <mdblac...@yahoo.com>
Subject: Re: [wsjt-devel] Disa
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
net>
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
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 match
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
. Re: Disable Tx after RRR/73 (ANDY DURBIN)
--
Message: 1
Date: Mon, 2 Jan 2017 16:55:43 +
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...@classdes
ry 2, 2017 11:40 AM
Subject: RE: [wsjt-devel] Disable Tx after RRR/73
#yiv4780127622 #yiv4780127622 -- _filtered #yiv4780127622
{font-family:Helvetica;panose-1:2 11 6 4 2 2 2 2 2 4;} _filtered #yiv4780127622
{panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv4780127622
{font-family:Calibri;p
: 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 so
It was removed in 7442
de Mike W9MDB
From: Bill ND0B <n...@ockert.us>
To: 'WSJT software development' <wsjt-devel@lists.sourceforge.net>
Sent: Monday, January 2, 2017 11:17 AM
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
#yiv0617045516 #yiv0617045516
vel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
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 t
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
g 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
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
"I figur
ry 2, 2017 11:22 AM
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
"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
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 1
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
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.
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
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:
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 -
"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
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
"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
28 matches
Mail list logo
