"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 tool tip to "Toggle Auto Tx sequencing On/Off"
3. Change option "Disable TX after sending 73" to "Disable Auto TX on 73"
(allows for the fact that start of message, not end of message, is the trigger)
4. Change option tool tip from "Turn off automatic transmissions after sending
73 or any other free text message" to "Turn off automatic transmissions (Auto
TX) on starting a 73 or a free message including 73" (Original tool tip is not
accurate. Any free message that does not include 73 will not trigger)
73,
Andy k3wyc
________________________________
From: [email protected]
<[email protected]>
Sent: Monday, January 2, 2017 11:34 AM
To: [email protected]
Subject: wsjt-devel Digest, Vol 35, Issue 23
Send wsjt-devel mailing list submissions to
[email protected]
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
[email protected]
You can reach the person managing the list at
[email protected]
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 (Bill Somerville)
3. Re: MSK144 Timing Flag? (Bill Somerville)
4. Re: MSK144 Timing Flag? (Bill ND0B)
5. Re: MSK144 Timing Flag? (Gordon Higgins)
----------------------------------------------------------------------
Message: 1
Date: Mon, 2 Jan 2017 18:15:17 +0000
From: Bill Somerville <[email protected]>
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"
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 paint function but as
soon as you do that you disallow the use of the native version. This
then ends up looking quite nasty when you end up with a combination of
native and custom widgets. It works better with some than others but
progress bars are definitely ones that look bad in custom form.
73
Bill
G4WJS.
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Mon, 2 Jan 2017 18:16:52 +0000
From: Bill Somerville <[email protected]>
Subject: Re: [wsjt-devel] Disable Tx after RRR/73
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"
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 in the tool tips. The functionality is correctly described in
> the help file. It that is considered satisfactory there is nothing
> more to be said.
>
Hi Andy,
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.
73
Bill
G4WJS.
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 3
Date: Mon, 2 Jan 2017 18:19:38 +0000
From: Bill Somerville <[email protected]>
Subject: Re: [wsjt-devel] MSK144 Timing Flag?
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"
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? This will be an
> excellent opportunity for me to learn the ins and outs of packing in
> this new protocol.
HI Bill,
the CQ message does have an obvious set of permutations that are not
used. Joe recently added the interpretations of E9AA thru E9ZZ as CQ AA
thru CQ ZZ on the assumption that the E9 prefix will never be issued. I
think this leaves E9AAA thru E9ZZZ still spare and available for
interpretation, which is 26x26x26 permutations. The only thing I am not
sure of is if that is still true if the caller has a type 2 or type 3
compound callsign.
From the above you should see that the CQ message is just a "<his-call>
<my-call> <grid>" message with special meanings being applied to certain
<his-call> and <grid> combinations. "<his-call> <my-call> <report>"
messages use "<his-call> <my-call> <grid>" with spare space in the
<grid> component encoding to signify reports etc.
I hope I am right here but I think I have the general principles correct.
73
Bill
G4WJS.
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 4
Date: Mon, 2 Jan 2017 12:24:26 -0600
From: "Bill ND0B" <[email protected]>
Subject: Re: [wsjt-devel] MSK144 Timing Flag?
To: "'WSJT software development'" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
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:[email protected]]
Sent: Monday, January 2, 2017 12:20 PM
To: [email protected]
Subject: Re: [wsjt-devel] MSK144 Timing Flag?
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" This will be an excellent opportunity for
me to learn the ins and outs of packing in this new protocol.
HI Bill,
the CQ message does have an obvious set of permutations that are not used.
Joe recently added the interpretations of E9AA thru E9ZZ as CQ AA thru CQ ZZ
on the assumption that the E9 prefix will never be issued. I think this
leaves E9AAA thru E9ZZZ still spare and available for interpretation, which
is 26x26x26 permutations. The only thing I am not sure of is if that is
still true if the caller has a type 2 or type 3 compound callsign.
>From the above you should see that the CQ message is just a "<his-call>
<my-call> <grid>" message with special meanings being applied to certain
<his-call> and <grid> combinations. "<his-call> <my-call> <report>" messages
use "<his-call> <my-call> <grid>" with spare space in the <grid> component
encoding to signify reports etc.
I hope I am right here but I think I have the general principles correct.
73
Bill
G4WJS.
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 5
Date: Mon, 2 Jan 2017 18:33:52 +0000
From: Gordon Higgins <[email protected]>
Subject: Re: [wsjt-devel] MSK144 Timing Flag?
To: [email protected], WSJT software development
<[email protected]>
Message-ID:
<CADBfAVg4sYkQ4AywiYHf3gWUxvQZf127oabR=mMu=wzfiv3...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
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 <[email protected]> wrote:
> 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:[email protected]]
> *Sent:* Monday, January 2, 2017 12:20 PM
> *To:* [email protected]
> *Subject:* Re: [wsjt-devel] MSK144 Timing Flag?
>
>
>
> 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? This will be an excellent opportunity
> for me to learn the ins and outs of packing in this new protocol.
>
> HI Bill,
>
> the CQ message does have an obvious set of permutations that are not used.
> Joe recently added the interpretations of E9AA thru E9ZZ as CQ AA thru CQ
> ZZ on the assumption that the E9 prefix will never be issued. I think this
> leaves E9AAA thru E9ZZZ still spare and available for interpretation, which
> is 26x26x26 permutations. The only thing I am not sure of is if that is
> still true if the caller has a type 2 or type 3 compound callsign.
>
> From the above you should see that the CQ message is just a "<his-call>
> <my-call> <grid>" message with special meanings being applied to certain
> <his-call> and <grid> combinations. "<his-call> <my-call> <report>"
> messages use "<his-call> <my-call> <grid>" with spare space in the <grid>
> component encoding to signify reports etc.
>
> I hope I am right here but I think I have the general principles correct.
>
> 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
-------------- 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
End of wsjt-devel Digest, Vol 35, Issue 23
******************************************
------------------------------------------------------------------------------
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
