Re: [wsjt-devel] issue? report No change frequncy by FT8 to MSK144

[Bill Somerville]

On 21/11/2020 01:51, Yoshi,I wrote:

Hello
issue? report No change frequncy by FT8 to MSK144

When changing from FT8 to MSK144 at 50MHz, the frequency does not follow.
We have confirmed that 50.260MHz has been added to the frequency list MSK144.
When changing from FT8 toMSK144, the frequency list is updated, but the window 
displaying the
transmission frequency does not change from 50.313MHz of FT8.
However, if you manually change the MSK144 to 50.260MHz and then switch back to 
FT8,
the frequency will return to the listed 50.313MHz.
I checked it on another PC, but it was the same.
There was no change even if the IARU Region was changed to ALL or Region3.(Same 
operation)

Use OS Windows10
Thanks.
-- de JH8XVH Yoshi


Hi Yoshi san,

sorry for the delay of this reply. I can confirm that the failure of 
WSJT-X v2.3.0 RC2 to select the expected working frequency when changing 
to some modes is a regression. It is fixed for the next release.


73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Re-click on RRR or RR73

[Bill Somerville]

On 27/11/2020 13:52, Black Michael via wsjt-devel wrote:

What works.

In QSOpartner sends RRR or RR73 a 2nd time and you double-click 
then RR73 or 73 is selected to transmit.


What doesn't work
After you send your first RR73/73 you start a QSO with someone 
elseprevious partner resends RRR or RR73...you double-click and 
you get TX1.

It's been this way forever as far as I know.

What should happen...

Double-click on RRR or RR73 with your callsign in the message should 
send RR73/73.  Better chance of completing the QSO in the 1st 
transmission.


Mike W9MDB


Hi Mike,

although your suggestion seems attractive it would require a 
considerable change in the WSJT-X logic to correctly complete and offer 
correct logging details for such a "restarted" QSO. WSJT-X does not keep 
details of unfinished QSOs and therefore cannot know that a 
double-left-click of a message with a "new" QSO partner is anything 
other than an attempt to start a new QSO. that is why it selects the Tx1 
message as the next message to be transmitted. It is the operator's 
responsibility to track such "off-piste" scenarios and manually select 
the correct message to send. Further to this, a good operator should be 
aware of the likelihood, or otherwise, of a repeat message from a QSO 
partner and be prepared to act accordingly.


73
Bill
G4WJS.

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Minor bug in 2.3.0-rc2: Tooltip

[Bill Somerville]

On 28/11/2020 02:15, Dave Slotter, W3DJS wrote:

Greetings and Seasons' Tidings:

I noticed a very minor defect with the tooltips in 2.3.0-rc2 -- on the 
Raspberry Pi -- but I see no reason why it wouldn't be on other Linux 
platforms.


When in FT4 mode, there is no tooltip for the "Best S+P" button. All 
the other buttons I checked have tooltips.


Thank you for all you folks do on WSJT-X

--
Dave Slotter, W3DJS 


Hi Dave,

thanks for the issue report. A tool-tip has been added for that button 
for the next release.


73
Bill
G4WJS.

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Minor bug in 2.3.0-rc2: Tooltip

[Dave Slotter, W3DJS]

Excellent! Thank you, kind sir.

--
Dave Slotter, W3DJS 


On Tue, Dec 1, 2020 at 11:07 AM Bill Somerville 
wrote:

> On 28/11/2020 02:15, Dave Slotter, W3DJS wrote:
>
> Greetings and Seasons' Tidings:
>
> I noticed a very minor defect with the tooltips in 2.3.0-rc2 -- on the
> Raspberry Pi -- but I see no reason why it wouldn't be on other Linux
> platforms.
>
> When in FT4 mode, there is no tooltip for the "Best S+P" button. All the
> other buttons I checked have tooltips.
>
> Thank you for all you folks do on WSJT-X
>
> --
> Dave Slotter, W3DJS 
>
> Hi Dave,
>
> thanks for the issue report. A tool-tip has been added for that button for
> the next release.
>
> 73
> Bill
> G4WJS.
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Vertical size

[Black Michael via wsjt-devel]

Seems the current version rc2 (and perhaps older versions) doesn't shrink 
vertically as far as it used to.
Would prefer to be able to shrink it vertically -- really down to almost 
nothing on the decode lines so we can gain more vertical real estate.
Mike W9MDB

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Normally i would not go off subject, but..

[n2lo]

A broken cable was the final straw for the already badly damaged Arecibo 
Observatory's radio telescope in Puerto Rico. The massive structure's 900-ton 
instrument platform collapsed on Tuesday (Dec. 1) and landed on the 
1,000-foot-wide (305 meters) radio dish.

The cable parted at around 8 a.m. local time, Ramon Lugo, director of the 
Florida Space Institute (FSI) at the University of Central Florida, told 
Science magazine. The FSI manages the telescope, which is owned by the National 
Science Foundation (NSF). 
While details of the collapse are still forthcoming, the previous failures of 
two cables in August and November, respectively, placed an extra burden on the 
remaining support structures. During the past week, the cables that were still 
in place were rapidly unraveling, losing about one wire per day, Lugo told 
Science.




Sent from Xfinity Connect Application

-Original Message-

From: n...@comcast.net
To: wsjt-devel@lists.sourceforge.net
Sent: 2020-11-28 6:08:10 PM 
Subject: [wsjt-devel] Normally i would not go off subject, but..


Petition To Save Arecibo

 

https://petitions.whitehouse.gov/petition/petition-emergency-action-evaluate-and-stabilize-arecibo-radio-telescope

 

Please consider signing and sharing widely.




DE N2LO ~>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Vertical size

[Bill Somerville]

On 01/12/2020 17:42, Black Michael via wsjt-devel wrote:
Seems the current version rc2 (and perhaps older versions) doesn't 
shrink vertically as far as it used to.


Would prefer to be able to shrink it vertically -- really down to 
almost nothing on the decode lines so we can gain more vertical real 
estate.


Mike W9MDB


Hi Mike,

thanks for the issue report. It is fixed for the next release.

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Logged wrong report

[David - K2DBK]

Any thoughts here?

 

From: K2DBK-WSJT  
Sent: Sunday, November 29, 2020 10:54 AM
To: 'WSJT software development' 
Subject: [wsjt-devel] Logged wrong report

 

I'm not sure if this is a regression from a previous version, but running
v2.3.0-rc2 I had the following sequence:

 



 

You can see that I was sent -16 3 times, then C31VM sent +06 to another
station, and finally came back with RRR to me. However, the pre-filled
values in the logging dialog make it appear that he sent +06 to me, as
evidenced by the line from the log:

 

2020-11-28,23:28:45,2020-11-28,23:31:15,C31VM,JN02,7.075287,FT8,-13,+06

 

I have the .wav files for this sequence if that would be helpful.

 

-- 

73,

David, K2DBK

  http://k2dbk.com

twitter: @k2dbk

 

 

 

As an operator I know it's my responsibility to log the correct information,
but I'm guessing this isn't intended behavior.

 

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Getting WSJT-X version via command line

[Dave Slotter, W3DJS]

Hi Bill,

Thank you for all that you do for WSJT-X development. Because of your
contributions, tens of thousands (hundreds of thousands?) of amateur radio
operators enjoy operating digital modes with other amateur radio operators
around the globe.

That said, under Linux (and probably also for Mac and Windows), using
the command line, when I type in "wsjtx --version", a GUI dialog is
displayed with the WSJT-X version, but that doesn't help a shell script
trying to get the WSJT-X version programmatically.

I wrote an update script for Linux, and while it could in theory check the
version on the website and check the installed version and then determine
whether to download the newer version (or not), it is hampered by this
limitation.

I did discover that there is a version number stored in
$HOME/.config/WSJT-X.ini, but that is only a preference setting, and does
not guarantee the version installed. Likewise, under
$HOME/.local/share/WSJT-X/logs/wsjtx_syslog_-MM.log the program version
is logged upon application startup, but once again, that's not a guarantee
of installed version.

*May I please request that a) "wsjtx --version" return version string to
stdout and b) the operation is non-blocking?*

*While I'm at it, may I please additionally request that c) wsjtx --help
also output to stdout ?*

Is there an issue tracker for WSJT-X? I'd be happy to enter these concerns
into there directly. I went to SourceForge and didn't see any mechanism for
this.

Thanks and 73,

--
Dave Slotter, W3DJS 
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Two year old outstanding merge request

[Dave Slotter, W3DJS]

Bill,

When investigating through WSJT-X's pages in Sourceforge, I located an open
merge request (#3) from November 17, 2018. Is this intentional?

It's listed as "show full frequencies on scale in wspr mode".

Thanks and 73,

--
Dave Slotter, W3DJS 
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Sourceforge mentions CW as mode

[Dave Slotter, W3DJS]

Hi Bill / Joe,

On the main project page on Sourceforge:
https://sourceforge.net/projects/wsjt/ , it lists "CW" as a WSJT mode. I
don't see any mention of CW in the 2.3.0-rc1 documentation for WSJT-X.
However, looking at the WSJT (no "X") user guide, I do see CW mentioned as
being used for EME.

Is this still relevant?

Please advise and thank you.

73,

--
Dave Slotter, W3DJS 
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Getting WSJT-X version via command line

[Bill Somerville]

On 01/12/2020 21:02, Dave Slotter, W3DJS wrote:

Hi Bill,

Thank you for all that you do for WSJT-X development. Because of your 
contributions, tens of thousands (hundreds of thousands?) of amateur 
radio operators enjoy operating digital modes with other amateur radio 
operators around the globe.


That said, under Linux (and probably also for Mac and Windows), using 
the command line, when I type in "wsjtx --version", a GUI dialog is 
displayed with the WSJT-X version, but that doesn't help a shell 
script trying to get the WSJT-X version programmatically.


I wrote an update script for Linux, and while it could in theory check 
the version on the website and check the installed version and then 
determine whether to download the newer version (or not), it is 
hampered by this limitation.


I did discover that there is a version number stored in 
$HOME/.config/WSJT-X.ini, but that is only a preference setting, and 
does not guarantee the version installed. Likewise, under 
$HOME/.local/share/WSJT-X/logs/wsjtx_syslog_-MM.log the program 
version is logged upon application startup, but once again, that's not 
a guarantee of installed version.


*May I please request that a) "wsjtx --version" return version string 
to stdout and b) the operation is non-blocking?*


*While I'm at it, may I please additionally request that c) 
wsjtx --help also output to stdout ?*


Is there an issue tracker for WSJT-X? I'd be happy to enter these 
concerns into there directly. I went to SourceForge and didn't see any 
mechanism for this.


Thanks and 73,

--
Dave Slotter, W3DJS 


Hi Dave,

that would have to be a non-Windows platform only change, in fact 
non-macOS as well really. Windows and macOS don't normally have a 
console attached when running the application. It would be easier to 
provide a command line tool packaged with WSJT-X that did what you are 
looking for.


73
Bill
G4WJS.

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Sourceforge mentions CW as mode

[Joe Taylor]

Dave --

WSJT does have (limited) support for CW.  A few people used it -- only 
for EME, as far as I know.  WSJT-X has never supported CW beyond sending 
an optional CW ID in some modes.


-- Joe, K1JT

On 12/1/2020 4:18 PM, Dave Slotter, W3DJS wrote:

Hi Bill / Joe,

On the main project page on Sourceforge: 
https://sourceforge.net/projects/wsjt/ , it lists "CW" as a WSJT mode. I 
don't see any mention of CW in the 2.3.0-rc1 documentation for WSJT-X. 
However, looking at the WSJT (no "X") user guide, I do see CW mentioned 
as being used for EME.


Is this still relevant?

Please advise and thank you.

73,

--
Dave Slotter, W3DJS 


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Getting WSJT-X version via command line

[Dave Slotter, W3DJS]

Bill,

Do you want me to volunteer to write it?

--
Dave Slotter, W3DJS 


On Tue, Dec 1, 2020 at 4:53 PM Bill Somerville 
wrote:

> On 01/12/2020 21:02, Dave Slotter, W3DJS wrote:
>
> Hi Bill,
>
> Thank you for all that you do for WSJT-X development. Because of your
> contributions, tens of thousands (hundreds of thousands?) of amateur radio
> operators enjoy operating digital modes with other amateur radio operators
> around the globe.
>
> That said, under Linux (and probably also for Mac and Windows), using
> the command line, when I type in "wsjtx --version", a GUI dialog is
> displayed with the WSJT-X version, but that doesn't help a shell script
> trying to get the WSJT-X version programmatically.
>
> I wrote an update script for Linux, and while it could in theory check the
> version on the website and check the installed version and then determine
> whether to download the newer version (or not), it is hampered by this
> limitation.
>
> I did discover that there is a version number stored in
> $HOME/.config/WSJT-X.ini, but that is only a preference setting, and does
> not guarantee the version installed. Likewise, under
> $HOME/.local/share/WSJT-X/logs/wsjtx_syslog_-MM.log the program version
> is logged upon application startup, but once again, that's not a guarantee
> of installed version.
>
> *May I please request that a) "wsjtx --version" return version string to
> stdout and b) the operation is non-blocking?*
>
> *While I'm at it, may I please additionally request that c) wsjtx --help
> also output to stdout ?*
>
> Is there an issue tracker for WSJT-X? I'd be happy to enter these concerns
> into there directly. I went to SourceForge and didn't see any mechanism for
> this.
>
> Thanks and 73,
>
> --
> Dave Slotter, W3DJS 
>
> Hi Dave,
>
> that would have to be a non-Windows platform only change, in fact
> non-macOS as well really. Windows and macOS don't normally have a console
> attached when running the application. It would be easier to provide a
> command line tool packaged with WSJT-X that did what you are looking for.
>
> 73
> Bill
> G4WJS.
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Sourceforge mentions CW as mode

[Dave Slotter, W3DJS]

I was just wondering if it is still relevant to mention WSJT on
Sourceforge. The only code I see on Sourceforge is WSJT-X. (Please correct
me if I am wrong.)

--
Dave Slotter, W3DJS 


On Tue, Dec 1, 2020 at 5:06 PM Joe Taylor  wrote:

> Dave --
>
> WSJT does have (limited) support for CW.  A few people used it -- only
> for EME, as far as I know.  WSJT-X has never supported CW beyond sending
> an optional CW ID in some modes.
>
> -- Joe, K1JT
>
> On 12/1/2020 4:18 PM, Dave Slotter, W3DJS wrote:
> > Hi Bill / Joe,
> >
> > On the main project page on Sourceforge:
> > https://sourceforge.net/projects/wsjt/ , it lists "CW" as a WSJT mode.
> I
> > don't see any mention of CW in the 2.3.0-rc1 documentation for WSJT-X.
> > However, looking at the WSJT (no "X") user guide, I do see CW mentioned
> > as being used for EME.
> >
> > Is this still relevant?
> >
> > Please advise and thank you.
> >
> > 73,
> >
> > --
> > Dave Slotter, W3DJS 
> >
> >
> > ___
> > wsjt-devel mailing list
> > wsjt-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> >
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Sourceforge mentions CW as mode

[Bill Somerville]

Hi Dave,

you are wrong, the sources for all the applications for weak signal 
modes is available from the WSJT SourceForge project site.


https://sourceforge.net/p/wsjt/_list/git

73
Bill
G4WJS.

On 01/12/2020 22:26, Dave Slotter, W3DJS wrote:
I was just wondering if it is still relevant to mention WSJT on 
Sourceforge. The only code I see on Sourceforge is WSJT-X. (Please 
correct me if I am wrong.)


--
Dave Slotter, W3DJS 


On Tue, Dec 1, 2020 at 5:06 PM Joe Taylor > wrote:


Dave --

WSJT does have (limited) support for CW.  A few people used it --
only
for EME, as far as I know.  WSJT-X has never supported CW beyond
sending
an optional CW ID in some modes.

        -- Joe, K1JT

On 12/1/2020 4:18 PM, Dave Slotter, W3DJS wrote:
> Hi Bill / Joe,
>
> On the main project page on Sourceforge:
> https://sourceforge.net/projects/wsjt/
 , it lists "CW" as a WSJT
mode. I
> don't see any mention of CW in the 2.3.0-rc1 documentation for
WSJT-X.
> However, looking at the WSJT (no "X") user guide, I do see CW
mentioned
> as being used for EME.
>
> Is this still relevant?
>
> Please advise and thank you.
>
> 73,
>
> --
> Dave Slotter, W3DJS >



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Sourceforge mentions CW as mode

[Dave Slotter, W3DJS]

Thanks for showing me where to find them. I was looking under the "Files"
section and didn't spot them. Didn't think to look under git.

--
Dave Slotter, W3DJS 


On Tue, Dec 1, 2020 at 5:47 PM Bill Somerville 
wrote:

> Hi Dave,
>
> you are wrong, the sources for all the applications for weak signal modes
> is available from the WSJT SourceForge project site.
>
> https://sourceforge.net/p/wsjt/_list/git
>
> 73
> Bill
> G4WJS.
>
> On 01/12/2020 22:26, Dave Slotter, W3DJS wrote:
>
> I was just wondering if it is still relevant to mention WSJT on
> Sourceforge. The only code I see on Sourceforge is WSJT-X. (Please correct
> me if I am wrong.)
>
> --
> Dave Slotter, W3DJS 
>
>
> On Tue, Dec 1, 2020 at 5:06 PM Joe Taylor  wrote:
>
>> Dave --
>>
>> WSJT does have (limited) support for CW.  A few people used it -- only
>> for EME, as far as I know.  WSJT-X has never supported CW beyond sending
>> an optional CW ID in some modes.
>>
>> -- Joe, K1JT
>>
>> On 12/1/2020 4:18 PM, Dave Slotter, W3DJS wrote:
>> > Hi Bill / Joe,
>> >
>> > On the main project page on Sourceforge:
>> > https://sourceforge.net/projects/wsjt/ , it lists "CW" as a WSJT mode.
>> I
>> > don't see any mention of CW in the 2.3.0-rc1 documentation for WSJT-X.
>> > However, looking at the WSJT (no "X") user guide, I do see CW mentioned
>> > as being used for EME.
>> >
>> > Is this still relevant?
>> >
>> > Please advise and thank you.
>> >
>> > 73,
>> >
>> > --
>> > Dave Slotter, W3DJS 
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Getting WSJT-X version via command line

[Dave Slotter, W3DJS]

Bill,

Ok, I volunteered myself to write it. It works and seems to reasonably fit
within the existing Qt / CMake environment.

How do I get the changes to you? AppVersion.cpp is 49 lines long and
CMakeLists.txt has 10 new lines.

Do you want a Git pull request or do you want a patch file or should I just
send the changed files as attachments?

Please advise, and thanks.

--
Dave Slotter, W3DJS 


On Tue, Dec 1, 2020 at 5:25 PM Dave Slotter, W3DJS 
wrote:

> Bill,
>
> Do you want me to volunteer to write it?
>
> --
> Dave Slotter, W3DJS 
>
>
> On Tue, Dec 1, 2020 at 4:53 PM Bill Somerville 
> wrote:
>
>> On 01/12/2020 21:02, Dave Slotter, W3DJS wrote:
>>
>> Hi Bill,
>>
>> Thank you for all that you do for WSJT-X development. Because of your
>> contributions, tens of thousands (hundreds of thousands?) of amateur radio
>> operators enjoy operating digital modes with other amateur radio operators
>> around the globe.
>>
>> That said, under Linux (and probably also for Mac and Windows), using
>> the command line, when I type in "wsjtx --version", a GUI dialog is
>> displayed with the WSJT-X version, but that doesn't help a shell script
>> trying to get the WSJT-X version programmatically.
>>
>> I wrote an update script for Linux, and while it could in theory check
>> the version on the website and check the installed version and then
>> determine whether to download the newer version (or not), it is hampered by
>> this limitation.
>>
>> I did discover that there is a version number stored in
>> $HOME/.config/WSJT-X.ini, but that is only a preference setting, and does
>> not guarantee the version installed. Likewise, under
>> $HOME/.local/share/WSJT-X/logs/wsjtx_syslog_-MM.log the program version
>> is logged upon application startup, but once again, that's not a guarantee
>> of installed version.
>>
>> *May I please request that a) "wsjtx --version" return version string to
>> stdout and b) the operation is non-blocking?*
>>
>> *While I'm at it, may I please additionally request that c) wsjtx --help
>> also output to stdout ?*
>>
>> Is there an issue tracker for WSJT-X? I'd be happy to enter these
>> concerns into there directly. I went to SourceForge and didn't see any
>> mechanism for this.
>>
>> Thanks and 73,
>>
>> --
>> Dave Slotter, W3DJS 
>>
>> Hi Dave,
>>
>> that would have to be a non-Windows platform only change, in fact
>> non-macOS as well really. Windows and macOS don't normally have a console
>> attached when running the application. It would be easier to provide a
>> command line tool packaged with WSJT-X that did what you are looking for.
>>
>> 73
>> Bill
>> G4WJS.
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Getting WSJT-X version via command line

[Bill Somerville]

Hi Dave,

a universal diff patch against the current SourceForge git repo master 
branch is fine as it is a small change.


73
Bill
G4WJS.

On 02/12/2020 00:54, Dave Slotter, W3DJS wrote:

Bill,

Ok, I volunteered myself to write it. It works and seems to reasonably 
fit within the existing Qt / CMake environment.


How do I get the changes to you? AppVersion.cpp is 49 lines long and 
CMakeLists.txt has 10 new lines.


Do you want a Git pull request or do you want a patch file or should I 
just send the changed files as attachments?


Please advise, and thanks.

--
Dave Slotter, W3DJS 


On Tue, Dec 1, 2020 at 5:25 PM Dave Slotter, W3DJS 
mailto:slotter%2bw3...@gmail.com>> wrote:


Bill,

Do you want me to volunteer to write it?

-- 
Dave Slotter, W3DJS 



On Tue, Dec 1, 2020 at 4:53 PM Bill Somerville
mailto:g4...@classdesign.com>> wrote:

On 01/12/2020 21:02, Dave Slotter, W3DJS wrote:

Hi Bill,

Thank you for all that you do for WSJT-X development. Because
of your contributions, tens of thousands (hundreds of
thousands?) of amateur radio operators enjoy operating
digital modes with other amateur radio operators around the
globe.

That said, under Linux (and probably also for Mac and
Windows), using the command line, when I type in
"wsjtx --version", a GUI dialog is displayed with the WSJT-X
version, but that doesn't help a shell script trying to get
the WSJT-X version programmatically.

I wrote an update script for Linux, and while it could in
theory check the version on the website and check the
installed version and then determine whether to download the
newer version (or not), it is hampered by this limitation.

I did discover that there is a version number stored in
$HOME/.config/WSJT-X.ini, but that is only a preference
setting, and does not guarantee the version installed.
Likewise, under
$HOME/.local/share/WSJT-X/logs/wsjtx_syslog_-MM.log the
program version is logged upon application startup, but once
again, that's not a guarantee of installed version.

*May I please request that a) "wsjtx --version" return
version string to stdout and b) the operation is non-blocking?*

*While I'm at it, may I please additionally request that c)
wsjtx --help also output to stdout ?*

Is there an issue tracker for WSJT-X? I'd be happy to enter
these concerns into there directly. I went to SourceForge and
didn't see any mechanism for this.

Thanks and 73,

-- 
Dave Slotter, W3DJS 


Hi Dave,

that would have to be a non-Windows platform only change, in
fact non-macOS as well really. Windows and macOS don't
normally have a console attached when running the application.
It would be easier to provide a command line tool packaged
with WSJT-X that did what you are looking for.

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSPR Band Hopping

[David Birnbaum]

Glad to report that the crashes with 2.2.2 when band hopping in WSPR seems
to be fixed in 2.3.0-rc2

dave
k2lyv
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Getting WSJT-X version via command line

[Dave Slotter, W3DJS]

Bill,

Please see attached files:

CMakeLists.txt.patch
AppVersion/AppVersion.cpp

Please let me know if you have any questions.

73,

--
Dave Slotter, W3DJS 


On Tue, Dec 1, 2020 at 8:04 PM Bill Somerville 
wrote:

> Hi Dave,
>
> a universal diff patch against the current SourceForge git repo master
> branch is fine as it is a small change.
>
> 73
> Bill
> G4WJS.
>
> On 02/12/2020 00:54, Dave Slotter, W3DJS wrote:
>
> Bill,
>
> Ok, I volunteered myself to write it. It works and seems to reasonably fit
> within the existing Qt / CMake environment.
>
> How do I get the changes to you? AppVersion.cpp is 49 lines long and
> CMakeLists.txt has 10 new lines.
>
> Do you want a Git pull request or do you want a patch file or should I
> just send the changed files as attachments?
>
> Please advise, and thanks.
>
> --
> Dave Slotter, W3DJS 
>
>
> On Tue, Dec 1, 2020 at 5:25 PM Dave Slotter, W3DJS <
> slotter+w3...@gmail.com> wrote:
>
>> Bill,
>>
>> Do you want me to volunteer to write it?
>>
>> --
>> Dave Slotter, W3DJS 
>>
>>
>> On Tue, Dec 1, 2020 at 4:53 PM Bill Somerville 
>> wrote:
>>
>>> On 01/12/2020 21:02, Dave Slotter, W3DJS wrote:
>>>
>>> Hi Bill,
>>>
>>> Thank you for all that you do for WSJT-X development. Because of your
>>> contributions, tens of thousands (hundreds of thousands?) of amateur radio
>>> operators enjoy operating digital modes with other amateur radio operators
>>> around the globe.
>>>
>>> That said, under Linux (and probably also for Mac and Windows), using
>>> the command line, when I type in "wsjtx --version", a GUI dialog is
>>> displayed with the WSJT-X version, but that doesn't help a shell script
>>> trying to get the WSJT-X version programmatically.
>>>
>>> I wrote an update script for Linux, and while it could in theory check
>>> the version on the website and check the installed version and then
>>> determine whether to download the newer version (or not), it is hampered by
>>> this limitation.
>>>
>>> I did discover that there is a version number stored in
>>> $HOME/.config/WSJT-X.ini, but that is only a preference setting, and does
>>> not guarantee the version installed. Likewise, under
>>> $HOME/.local/share/WSJT-X/logs/wsjtx_syslog_-MM.log the program version
>>> is logged upon application startup, but once again, that's not a guarantee
>>> of installed version.
>>>
>>> *May I please request that a) "wsjtx --version" return version string to
>>> stdout and b) the operation is non-blocking?*
>>>
>>> *While I'm at it, may I please additionally request that c) wsjtx --help
>>> also output to stdout ?*
>>>
>>> Is there an issue tracker for WSJT-X? I'd be happy to enter these
>>> concerns into there directly. I went to SourceForge and didn't see any
>>> mechanism for this.
>>>
>>> Thanks and 73,
>>>
>>> --
>>> Dave Slotter, W3DJS 
>>>
>>> Hi Dave,
>>>
>>> that would have to be a non-Windows platform only change, in fact
>>> non-macOS as well really. Windows and macOS don't normally have a console
>>> attached when running the application. It would be easier to provide a
>>> command line tool packaged with WSJT-X that did what you are looking for.
>>>
>>> 73
>>> Bill
>>> G4WJS.
>>>
>>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
pi@hampi:~/hamradio/wsjtx $ cat AppVersion/AppVersion.cpp
//
// wsjtx_app_version - a console application that outputs WSJT-X
// application version
//
// This application is only provided as a simple console application
//
//

#include 
#include 

#include 
#include 
#include 

#include "qt_helpers.hpp"
#include "revision_utils.hpp"


int main (int argc, char * argv[])
{
  QCoreApplication app {argc, argv};
  try
{
  setlocale (LC_NUMERIC, "C"); // ensure number forms are in
   // consistent format, do this after
   // instantiating QApplication so
   // that GUI has correct l18n

  app.setApplicationName ("WSJT-X");
  app.setApplicationVersion (version());

  QCommandLineParser parser;
//  parser.setApplicationDescription ("\n" PROJECT_DESCRIPTION);
  auto help_option = parser.addHelpOption ();
  auto version_option = parser.addVersionOption ();

  parser.process (app);

  catch (std::exception const & e)
{
  std::cerr << "Error: " << e.what () << '\n';
}
  catch (...)
{
  std::cerr << "Unexpected error\n";
}
  return -1;
}
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 72c38fa13..da1a1f929 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -1458,6 +1458,15 @@ generate_version_info (udp_daemon_VERSION_RESOURCES
 add_executable (udp_daemon UDPExamples/UDPDaemon.cpp ${udp_daemon_VERSION_RESOURCES})
 target_link_libraries (udp_dae

Re: [wsjt-devel] Getting WSJT-X version via command line

[Bill Somerville]

Hi Dave,

thanks for that, good job. Pruned it down a bit as I had to edit it to 
make it compile, hi. It's in for the next release.


For next time it is quicker and easier to integrate if you simply do:

git diff >file.patch


from the root of the source tree to make a combined unified diff patch file.

73
Bill
G4WJS.

On 02/12/2020 01:31, Dave Slotter, W3DJS wrote:

Bill,

Please see attached files:

CMakeLists.txt.patch
AppVersion/AppVersion.cpp

Please let me know if you have any questions.

73,

--
Dave Slotter, W3DJS 


On Tue, Dec 1, 2020 at 8:04 PM Bill Somerville > wrote:


Hi Dave,

a universal diff patch against the current SourceForge git repo
master branch is fine as it is a small change.

73
Bill
G4WJS.

On 02/12/2020 00:54, Dave Slotter, W3DJS wrote:

Bill,

Ok, I volunteered myself to write it. It works and seems to
reasonably fit within the existing Qt / CMake environment.

How do I get the changes to you? AppVersion.cpp is 49 lines long
and CMakeLists.txt has 10 new lines.

Do you want a Git pull request or do you want a patch file or
should I just send the changed files as attachments?

Please advise, and thanks.

-- 
Dave Slotter, W3DJS 



On Tue, Dec 1, 2020 at 5:25 PM Dave Slotter, W3DJS
mailto:slotter%2bw3...@gmail.com>> wrote:

Bill,

Do you want me to volunteer to write it?

-- 
Dave Slotter, W3DJS 



On Tue, Dec 1, 2020 at 4:53 PM Bill Somerville
mailto:g4...@classdesign.com>> wrote:

On 01/12/2020 21:02, Dave Slotter, W3DJS wrote:

Hi Bill,

Thank you for all that you do for WSJT-X development.
Because of your contributions, tens of thousands
(hundreds of thousands?) of amateur radio operators
enjoy operating digital modes with other amateur radio
operators around the globe.

That said, under Linux (and probably also for Mac and
Windows), using the command line, when I type in
"wsjtx --version", a GUI dialog is displayed with the
WSJT-X version, but that doesn't help a shell script
trying to get the WSJT-X version programmatically.

I wrote an update script for Linux, and while it could
in theory check the version on the website and check the
installed version and then determine whether to download
the newer version (or not), it is hampered by this
limitation.

I did discover that there is a version number stored in
$HOME/.config/WSJT-X.ini, but that is only a preference
setting, and does not guarantee the version installed.
Likewise, under
$HOME/.local/share/WSJT-X/logs/wsjtx_syslog_-MM.log
the program version is logged upon application startup,
but once again, that's not a guarantee of installed version.

*May I please request that a) "wsjtx --version" return
version string to stdout and b) the operation is
non-blocking?*

*While I'm at it, may I please additionally request that
c) wsjtx --help also output to stdout ?*

Is there an issue tracker for WSJT-X? I'd be happy to
enter these concerns into there directly. I went to
SourceForge and didn't see any mechanism for this.

Thanks and 73,

-- 
Dave Slotter, W3DJS 


Hi Dave,

that would have to be a non-Windows platform only change,
in fact non-macOS as well really. Windows and macOS don't
normally have a console attached when running the
application. It would be easier to provide a command line
tool packaged with WSJT-X that did what you are looking for.

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Getting WSJT-X version via command line

[Dave Slotter, W3DJS]

Bill,

I tried that but it wouldn't pick up the new file for some reason. It only
got the changes to CMakeList.txt . Maybe I did something wrong?

73,

On Tue, Dec 1, 2020, 9:10 PM Bill Somerville  wrote:

> Hi Dave,
>
> thanks for that, good job. Pruned it down a bit as I had to edit it to
> make it compile, hi. It's in for the next release.
>
> For next time it is quicker and easier to integrate if you simply do:
>
> git diff >file.patch
>
>
> from the root of the source tree to make a combined unified diff patch
> file.
>
> 73
> Bill
> G4WJS.
>
> On 02/12/2020 01:31, Dave Slotter, W3DJS wrote:
>
> Bill,
>
> Please see attached files:
>
> CMakeLists.txt.patch
> AppVersion/AppVersion.cpp
>
> Please let me know if you have any questions.
>
> 73,
>
> --
> Dave Slotter, W3DJS 
>
>
> On Tue, Dec 1, 2020 at 8:04 PM Bill Somerville 
> wrote:
>
>> Hi Dave,
>>
>> a universal diff patch against the current SourceForge git repo master
>> branch is fine as it is a small change.
>>
>> 73
>> Bill
>> G4WJS.
>>
>> On 02/12/2020 00:54, Dave Slotter, W3DJS wrote:
>>
>> Bill,
>>
>> Ok, I volunteered myself to write it. It works and seems to reasonably
>> fit within the existing Qt / CMake environment.
>>
>> How do I get the changes to you? AppVersion.cpp is 49 lines long and
>> CMakeLists.txt has 10 new lines.
>>
>> Do you want a Git pull request or do you want a patch file or should I
>> just send the changed files as attachments?
>>
>> Please advise, and thanks.
>>
>> --
>> Dave Slotter, W3DJS 
>>
>>
>> On Tue, Dec 1, 2020 at 5:25 PM Dave Slotter, W3DJS <
>> slotter+w3...@gmail.com> wrote:
>>
>>> Bill,
>>>
>>> Do you want me to volunteer to write it?
>>>
>>> --
>>> Dave Slotter, W3DJS 
>>>
>>>
>>> On Tue, Dec 1, 2020 at 4:53 PM Bill Somerville 
>>> wrote:
>>>
 On 01/12/2020 21:02, Dave Slotter, W3DJS wrote:

 Hi Bill,

 Thank you for all that you do for WSJT-X development. Because of your
 contributions, tens of thousands (hundreds of thousands?) of amateur radio
 operators enjoy operating digital modes with other amateur radio operators
 around the globe.

 That said, under Linux (and probably also for Mac and Windows), using
 the command line, when I type in "wsjtx --version", a GUI dialog is
 displayed with the WSJT-X version, but that doesn't help a shell script
 trying to get the WSJT-X version programmatically.

 I wrote an update script for Linux, and while it could in theory check
 the version on the website and check the installed version and then
 determine whether to download the newer version (or not), it is hampered by
 this limitation.

 I did discover that there is a version number stored in
 $HOME/.config/WSJT-X.ini, but that is only a preference setting, and does
 not guarantee the version installed. Likewise, under
 $HOME/.local/share/WSJT-X/logs/wsjtx_syslog_-MM.log the program version
 is logged upon application startup, but once again, that's not a guarantee
 of installed version.

 *May I please request that a) "wsjtx --version" return version string
 to stdout and b) the operation is non-blocking?*

 *While I'm at it, may I please additionally request that c)
 wsjtx --help also output to stdout ?*

 Is there an issue tracker for WSJT-X? I'd be happy to enter these
 concerns into there directly. I went to SourceForge and didn't see any
 mechanism for this.

 Thanks and 73,

 --
 Dave Slotter, W3DJS 

 Hi Dave,

 that would have to be a non-Windows platform only change, in fact
 non-macOS as well really. Windows and macOS don't normally have a console
 attached when running the application. It would be easier to provide a
 command line tool packaged with WSJT-X that did what you are looking for.

 73
 Bill
 G4WJS.

>>>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Getting WSJT-X version via command line

[Bill Somerville]

Hi Dave,

you need to stage the files. You can un-stage them after if you wish. 
The diff command becomes:


git diff --staged >file.patch

73
Bill
G4WJS.

On 02/12/2020 02:25, Dave Slotter, W3DJS wrote:

Bill,

I tried that but it wouldn't pick up the new file for some reason. It 
only got the changes to CMakeList.txt . Maybe I did something wrong?


73,

On Tue, Dec 1, 2020, 9:10 PM Bill Somerville > wrote:


Hi Dave,

thanks for that, good job. Pruned it down a bit as I had to edit
it to make it compile, hi. It's in for the next release.

For next time it is quicker and easier to integrate if you simply do:

git diff >file.patch


from the root of the source tree to make a combined unified diff
patch file.

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Getting WSJT-X version via command line

[Dave Slotter, W3DJS]

Ahhh! Thank you.

On Tue, Dec 1, 2020, 9:34 PM Bill Somerville  wrote:

> Hi Dave,
>
> you need to stage the files. You can un-stage them after if you wish. The
> diff command becomes:
>
> git diff --staged >file.patch
>
> 73
> Bill
> G4WJS.
>
> On 02/12/2020 02:25, Dave Slotter, W3DJS wrote:
>
> Bill,
>
> I tried that but it wouldn't pick up the new file for some reason. It only
> got the changes to CMakeList.txt . Maybe I did something wrong?
>
> 73,
>
> On Tue, Dec 1, 2020, 9:10 PM Bill Somerville 
> wrote:
>
>> Hi Dave,
>>
>> thanks for that, good job. Pruned it down a bit as I had to edit it to
>> make it compile, hi. It's in for the next release.
>>
>> For next time it is quicker and easier to integrate if you simply do:
>>
>> git diff >file.patch
>>
>>
>> from the root of the source tree to make a combined unified diff patch
>> file.
>>
>> 73
>> Bill
>> G4WJS.
>>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel