date:20200511

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

2020-05-11 Thread on4ckt

Joe,
thanks I found the 2.2.0 rc1 version. I'm going to work.

Kind regards.

ON4CKT Rudy

- Oorspronkelijk bericht -
Van: "Joe Taylor"
Aan: "wsjt-devel"
Verzonden: Maandag 11 mei 2020 16:44:33
Onderwerp: [wsjt-devel] WSJT-X 2.2.0-rc1

WSJT-X 2.2.0 will be a significant program upgrade offering many new
features.

The first candidate release, WSJT-X 2.2.0-rc1, is now available for
download and use by beta testers. This candidate release is your first
chance to test the new features and provide feedback to the WSJT
Development Group.

A list of program changes since WSJT-X 2.1.2 can be found in the
cumulative Release Notes
http://physics.princeton.edu/pulsar/k1jt/Release_Notes.txt
... and also in the updated WSJT-X 2.2.0 User Guide here:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.0-rc1.html#NEW_FEATURES

Upgrading from earlier versions of WSJT-X should be seamless. There is
no need to uninstall a previous version or move any files. You might
want to install to a different directory from your WSJT-X 2.1.2
installation.

Links to installation packages for Windows, Linux, and Macintosh are
available here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
Scroll down to find "Candidate release: WSJT-X 2.2.0-rc1".

You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/
It may take a short time for the SourceForge site to be updated.

WSJT-X is licensed under the terms of Version 3 of the GNU General
Public License (GPL). Development of this software is a cooperative
project to which many amateur radio operators have contributed. If you
use our code, please have the courtesy to let us know about it. If you
find bugs or make improvements to the code, please report them to us in
a timely fashion.

We hope you will enjoy using this beta release of WSJT-X 2.2.0. Please
report bugs by following instructions found here in the User Guide:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.0-rc1.html#_bug_reports

-- 73 from Joe, K1JT, Steve, K9AN, and Bill, G4WJS, for the
WSJT Development Group

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

Re: [wsjt-devel] Interesting new Band Activity operation

2020-05-11 Thread on4ckt

Hello, where can I download the WSJT-X 2.2.0rc1? I have seen on Joe's site but 
I find nothing there. Like info. 

Kind regards 
ON4CKT Rudy 


Van: "WB5JJJ"  
Aan: "wsjt-devel"  
Verzonden: Maandag 11 mei 2020 16:37:25 
Onderwerp: [wsjt-devel] Interesting new Band Activity operation 

Just installed v2.2.0 rc1 and found that the Band Activity window has a "new 
normal" that I find awkward. 

After the first decode period at 11.8s, the window works exactly as before, but 
at the conconsulsion of ALL decodes at ~15s, it resets the display to show only 
those last decoded. You must scroll up to see the original (larger) list of 
decodes. 

Temporary solution under Settings is to uncheck "Start new period decodes at 
top". Now you have a continuous flow of decodes (old way). I really enjoyed the 
start new decodes with the overflow off the bottom of the BA window, a much 
smaller list typically. I have part of the monitor display real estate taken up 
by JTAlert with just 3 lines of decodes, docked above WSJTx. 
-- 
George - WB5JJJ 


4 


___ 
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] v2.2.0 rc1 Dropdown Frequency list anomaly

2020-05-11 Thread Greg Vatt

Bill,

I know you are responding from an earlier email I sent but in my latest 
email I have now run the same tests on V2.2.0 and V.2.1.2. The results are 
different with V2.2.0 responding negatively to the scroll, but V.2.1.2 ignoring 
the scroll completely until the Frequency List dropdown appears).  Also, the 
I-beam doesn’t have to be present for the problem to occur (I only added that 
step to make sure everyone was testing the exact same case). Even if another 
text field is highlighted somewhere else on the page the mouse scroll still is 
acting on the Frequency Select Control in V2.2.0, but not V2.1.2.

This is a behavioral operating issue on my part but I was trying to 
flag a difference I found in V2.2.0 vs V2.1.2. I can’t duplicate this same 
negative behavior in V.2.1.2. 

I’m running all the tests on my Ham dedicated iMac (running macOS 
10.15.4). When you emailed I was in the process of downloading WSJT-X to my 
developer MacBook Pro (running macOS 10.15.5 Beta). I’ll see if that helps me 
learn anything new.

Thanks,

Greg  NC7B

> On May 11, 2020, at 6:33 PM, Bill Somerville  wrote:
> 
> On 11/05/2020 18:13, Greg Vatt wrote:
>> Bill,
>> 
>> I downloaded v2.2.0 rc1 without a hitch and everything seemed to be working 
>> fine. I tried it out on the air and quickly had a successful QSO. Then I 
>> went to change bands and that’s when something strange happened.
>> 
>> I went to the dropdown list to change the frequency and the frequencies 
>> appeared as they should. I have a number of frequencies so sometimes it is 
>> necessary to scroll up or down depending on where I currently am in the 
>> list. It worked OK the first time. However, if I tried to be too quick, by 
>> doing a mouse-down and mouse-move in rapid succession, WSJT-x started 
>> commanding my IC-7610 to reconfigure multiple times a second, jumping 
>> seemingly randomly to various frequencies. This goes on for a few seconds.
>> 
>> 
>> 
>> 
>> 
>> As long as the initial mouse-down is clean it seems to be working. However, 
>> after the first successful commanded frequency change, from that point on if 
>> I move the mouse to be anywhere within the outline of the frequency list 
>> (shown in red above) and then do a mouse-scroll only it starts the erratic 
>> frequency commanding behavior (no mouse-down to initiate). Sometimes it 
>> stops on its own, but more often it ends with the Rig Control Error popup to 
>> reconfigure the radio interface.
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> Greg  NC7B
>> 
>> 
>> Configuration:
>> 
>> macOS Catalina 10.15.4, (Multi-Touch surface mouse),  ICOM IC-7610
> Hi Greg,
> 
> AFAIK this is normal behaviour. A drop down combo box will respond to up and 
> down arrow keys and mouse wheel scrolls (or equivalents), when it has 
> keyboard focus (I-bar cursor in the edit field),  by selecting the previous 
> or next respective item from the drop down list. It doesn't matter if the 
> drop down list is visible.
> 
> 73
> Bill
> G4WJS.
> 

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

Re: [wsjt-devel] v2.2.0 rc1 Dropdown Frequency list anomaly

2020-05-11 Thread Greg Vatt

Scott,

I’ve been playing around some more and I found a sure-fire way to make this 
happen every time. I admit, It’s not the way one would operate normally, but it 
does cause the abnormal effect on V2.2.0 and also shows it doesn’t occur with 
V2.1.2.

First, the Good Way (works fine every time): Exaggeration of steps is 
intentional

Without your index finger on the mouse move the mouse over the down-arrow in 
the Frequency Select control.

With your index finger perform a mouse-down click on the down arrow.

Lift your index finger off the mouse until the drop-down frequency list is 
exposed.

Move the mouse arrow into the Frequency Select frequency list.

Now put your index finger back on the mouse surface.

Slide your finger forward/backward to highlight a new frequency

Now with your index finger do a mouse-down click to select the new frequency

The drop down then collapses and a new frequency is commanded to the radio. No 
Problems.

These steps are really exaggerated but they highlight the need to keep any 
index finger movements (even slight) from being interpreted as scroll commands

The Bad Way (on V2.2.0 only)

I’m not proposing this to be a correct way to operate but it does highlight my 
problem. It causes the problem on V2.2.0 but has no impact on V2.1.2

After successfully selecting a new frequency for the first time, now select a 
new frequency for a second time with the following steps:

Move the mouse away from the Frequency select control field (to any where else 
on the screen)

Now move the mouse back over the Frequency Select text area (important, the 
cursor must change to an I-Beam) while your index finger is on the mouse 
track-pad surface.

Do not do a mouse-down click

Instead, move your index finger forward/backward and that should trigger the 
abnormal behavior.

If you move your finger far it could trigger the Rig Control Error Alert, but 
at a minimum 
you should observe your radio being commanded to make multiple frequency 
changes.

Again, both of these tests are exaggerated but it reaches the two different 
outcomes. If you repeat the Bad Way on V2.1.2 the scroll is ignored and nothing 
bad happens. So I guess there isn’t a bad way in V2.1.2.

The good way is just an example of slowing down and taking deliberate steps 
when changing your frequency. The reality (for me) is I’m trying to 
select-mouse-click-scroll in one continuous motion while operating. It worked 
fine on V2.1.2 but has now got me in trouble on V2.2.0.

Greg  NC7B

> On May 11, 2020, at 5:14 PM, V. Scott Moore via wsjt-devel 
>  wrote:
> 
> From the peanut gallery:
> 
> I am running Catalina 10.15.3, Icom 7610 with the stock magic mouse with no 
> issues in the freq dropdown.
> The look of the dropdown has changed but functionality is good here.
> I will do the update to 10.15.4 tomorrow and if different I will post.
> 
> scott
> w1ssn
> 
>> On May 11, 2020, at 19:17, Greg Vatt mailto:n...@cox.net>> 
>> wrote:
>> 
>> Mike,
>> 
>> At my first attempt to avoid writing a long email and not give every single 
>> detail it appears I didn’t communicate my point well. What I experienced, 
>> first, did not occur in the prior versions of WSJT-X and second, it exposes 
>> a potential underlying difference (maybe problem?) with how the code might 
>> be handling the drop down frequency list now. 
>> 
>> Observation:
>> 
>> After I change the frequency for the first time it appears the software 
>> never completely releases the action after the popup completes the original 
>> frequency change. The Frequency drop down remains active even after the list 
>> is collapsed (probably because it is both a drop down list and an editable 
>> text field). If I happen to pass the mouse over the frequency box again (no 
>> mouse down - no frequency list exposed) it can trigger a spontaneous 
>> repeating of the software to reconfigure the radio (multiple times on 
>> different frequencies in rapid fashion) until I get the popup with the Rig 
>> Control Error message. The recovery mode is then to select cancel which 
>> force quits WSJT-X and then reboot again. I only discovered the odd 
>> scrolling behavior when I tried to stop the action by forcing the drop down 
>> list to be exposed again and then select any frequency to stop it. Every 
>> once in a while it stops everything at that point before the Rig Control 
>> Error message comes up.
>> 
>> Observation:
>> 
>> If I resume operation after a successful frequency change without clicking 
>> on any other text field or control on the WSJT-X page both the mouse-scroll 
>> and the keyboard up/down keys can still cause the frequency to change even 
>> though the Frequency drop down list is no longer exposed (maybe desired - 
>> but not the same behavior on a Mac as V2.1.2 - see below). If I select some 
>> other text field in the window then only the up/down keys are disabled from 
>> making a frequency change from that point on but the scroll of the

Re: [wsjt-devel] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

2020-05-11 Thread Bill Somerville


Hi OM,

the instructions in the sources tarball include this line:

$cmake-DWSJT_SKIP_MANPAGES=ON-DWSJT_GENERATE_DOCS=OFF../wsjtx-2.0.0

which includes the option settings to disable manpages and documentation 
generation, i.e. exactly what you needed apart from the version number 
on the unpacked tarball directory.


73
Bill
G4WJS.

On 12/05/2020 01:12, lgtngstk wrote:
That is good to know thanks. I was going by the information included 
in the tarball.


On Mon, May 11, 2020 at 6:49 PM Bill Somerville > wrote:


Hi OM,

OK, thanks for the update. We recommend end users disable the
manpages and documentation phase of the build, it is much easier
to do that than it is to get the required packages installed.

73
Bill
G4WJS.

On 11/05/2020 23:06, lgtngstk wrote:

Ok I finally got it to finish. It really did not want to make the
manpages. It was giving the a2x: ERROR: "xsltproc" error.

On Mon, May 11, 2020 at 5:49 PM lgtngstk mailto:lgtng...@gmail.com>> wrote:

Attempting compile under a Ubuntu distro cmake says the
following:
CMake Warning (dev) at CMakeLists.txt:165 (add_custom_target):
  Policy CMP0037 is not set: Target names should not be
reserved and should
  match a validity pattern.  Run "cmake --help-policy
CMP0037" for policy
  details.  Use the cmake_policy command to set the policy
and suppress this
  warning.

  The target name "install" is reserved or not valid for
certain CMake
  features, such as generator expressions, and may result in
undefined
  behavior.
This warning is for project developers.  Use -Wno-dev to
suppress it.

CMake Warning (dev) at CMakeLists.txt:166 (add_custom_target):
  Policy CMP0037 is not set: Target names should not be
reserved and should
  match a validity pattern.  Run "cmake --help-policy
CMP0037" for policy
  details.  Use the cmake_policy command to set the policy
and suppress this
  warning.

  The target name "package" is reserved or not valid for
certain CMake
  features, such as generator expressions, and may result in
undefined
  behavior.
This warning is for project developers.  Use -Wno-dev to
suppress it.

Which is fine since it does generate build files but later on
the compile fails with:
 [ 70%] Built target qcp
Makefile:149: recipe for target 'all' failed
make[3]: *** [all] Error 2
CMakeFiles/wsjtx-build.dir/build.make:60: recipe for target
'wsjtx-prefix/src/wsjtx-stamp/wsjtx-build' failed
make[2]: *** [wsjtx-prefix/src/wsjtx-stamp/wsjtx-build] Error 2
CMakeFiles/Makefile2:324: recipe for target
'CMakeFiles/wsjtx-build.dir/all' failed
make[1]: *** [CMakeFiles/wsjtx-build.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2

I don't know weather these things are related.



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

Re: [wsjt-devel] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

2020-05-11 Thread Bill Somerville


Hi David,

it's not very difficult, start with the self contained sources tarball 
from the WSJT-X project web page, unpack it and read the file INSTALL at 
the top level.


73
Bill
G4WJS.

On 12/05/2020 00:51, David Spoelstra wrote:

Thanks Bill. I might take a crack at building it...
-David, N9KT

On Mon, May 11, 2020 at 2:58 PM Bill Somerville > wrote:


Hi David,

as noted on the WSJT-X web page
https://physics.princeton.edu/pulsar/K1JT/wsjtx.html and in the
README info on the project SourceForge files area
https://sourceforge.net/projects/wsjt/files/wsjtx-2.2.0-rc1/ , the
Debian style packages target Ubuntu 18.04. Although Ubuntu 20.04
is released there is no easy upgrade path for users until the
20.04.1 release in a couple of months, until then we will target
the 18.04.x LTS release.

The Ubuntu package maintainers for WSJT-X will probably make
packages available soon that are suitable for various versions. In
the meantime you can build WSJT-X from sources.

73
Bill
G4WJS.

On 11/05/2020 19:21, David Spoelstra wrote:

As a follow-on, I did install "gfortran": sudo apt install
gfortran and got this:
Reading package lists... Done
Building dependency tree
Reading state information... Done
gfortran is already the newest version (4:9.3.0-1ubuntu2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

However I still get the error: "Depends: libgfortran3 (>= 4.8.2)
but it is not installable" when I try and install wsjt-x

Thanks!
-David, N9KT


On Mon, May 11, 2020 at 2:16 PM David Spoelstra
mailto:dav...@mediamachine.com>> wrote:

When I tried to install in the latest Ubuntu 20.04 LTS, I got:
The following packages have unmet dependencies:
 wsjtx : Depends: libgfortran3 (>= 4.8.2) but it is not
installable

When I try "sudo apt install libgfortran3" I get:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package libgfortran3

I'm a little lost as to how to get libgfortran3. Any suggestions?

Thanks!
-David, N9KT



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

Re: [wsjt-devel] v2.2.0 rc1 Dropdown Frequency list anomaly

2020-05-11 Thread V. Scott Moore via wsjt-devel

From the peanut gallery:

I am running Catalina 10.15.3, Icom 7610 with the stock magic mouse with no 
issues in the freq dropdown.
The look of the dropdown has changed but functionality is good here.
I will do the update to 10.15.4 tomorrow and if different I will post.

scott
w1ssn

> On May 11, 2020, at 19:17, Greg Vatt  wrote:
> 
> Mike,
> 
> At my first attempt to avoid writing a long email and not give every single 
> detail it appears I didn’t communicate my point well. What I experienced, 
> first, did not occur in the prior versions of WSJT-X and second, it exposes a 
> potential underlying difference (maybe problem?) with how the code might be 
> handling the drop down frequency list now. 
> 
> Observation:
> 
> After I change the frequency for the first time it appears the software never 
> completely releases the action after the popup completes the original 
> frequency change. The Frequency drop down remains active even after the list 
> is collapsed (probably because it is both a drop down list and an editable 
> text field). If I happen to pass the mouse over the frequency box again (no 
> mouse down - no frequency list exposed) it can trigger a spontaneous 
> repeating of the software to reconfigure the radio (multiple times on 
> different frequencies in rapid fashion) until I get the popup with the Rig 
> Control Error message. The recovery mode is then to select cancel which force 
> quits WSJT-X and then reboot again. I only discovered the odd scrolling 
> behavior when I tried to stop the action by forcing the drop down list to be 
> exposed again and then select any frequency to stop it. Every once in a while 
> it stops everything at that point before the Rig Control Error message comes 
> up.
> 
> Observation:
> 
> If I resume operation after a successful frequency change without clicking on 
> any other text field or control on the WSJT-X page both the mouse-scroll and 
> the keyboard up/down keys can still cause the frequency to change even though 
> the Frequency drop down list is no longer exposed (maybe desired - but not 
> the same behavior on a Mac as V2.1.2 - see below). If I select some other 
> text field in the window then only the up/down keys are disabled from making 
> a frequency change from that point on but the scroll of the Frequency List 
> (now hidden) still is operational if the mouse ventures into the Frequency 
> control field again. (Doesn’t matter if the cursor is blinking and active in 
> the Frequency Edit Field or blinking somewhere else on the page.)
> 
> (The behavior is the same for the up/down keys in V2.1.2, but V2.1.2 has the 
> mouse scroll disabled on
> a Mac for all conditions regarding frequency selection except when the 
> Frequency List is exposed.)
> 
> I’m hoping to communicate that one would think the new Frequency selection 
> would be determined when the Frequency selection list is opened on the first 
> mouse-click and then the new frequency choice is finalized on the second 
> mouse-click (when the list is collapsed again) no matter if the selection is 
> made by scrolling to the frequency choice or using the up/down keys. All of 
> these strange behaviors I’m experiencing can occur without the drop down list 
> ever being exposed. If the scrolling action can cause bad things to happen 
> then it shouldn’t be allowed in the code loop until after a drop down occurs 
> (that was the V2.1.2 behavior on a Mac).
> 
> On a Mac, the WSJT-X frequency selection is a single-finger, one-step, 
> no-mouse-move process, when using a Multi-Touch surface mouse. It becomes a 
> multi-step move and mouse click process when the up/down keys are involved. 
> So, I am just trying to take advantage of the simplified process that always 
> worked before. 
> 
> Summary:
> 
> I’m just trying to report new observations that did not happen to me with the 
> prior versions of WSJT-X while using my same operational pattern. This one 
> potentially could cause problems if it occurred during a QSO an a rig 
> reconfiguration was accidentally triggered. 
>  
> To end on a positive note, Thanks to the team for the hard work and overall 
> great product!  This new version is working great when I’m actually in a QSO 
> (and I keep my mouse away from the Frequency Selection area of the screen)!
> 
> 
> Greg  NC7B
> 
> 
> 
> 
>> On May 11, 2020, at 1:06 PM, Black Michael via wsjt-devel 
>> mailto:wsjt-devel@lists.sourceforge.net>> 
>> wrote:
>> 
>> Patient says...doc...it hurts when I do thisdoctor says...then don't do 
>> that.
>> 
>> What your doing is asking the list to scroll which changes the band which 
>> tells your rig to change bands.  You can do the same thing with the cursor 
>> up/down keys.
>> 
>> So don't do that.
>> 
>> de Mike W9MDB
>> 
>> 
>> 
>> 
>> On Monday, May 11, 2020, 12:18:59 PM CDT, Greg Vatt > > wrote:
>> 
>> 
>> Bill,
>> 
>> I downloaded v2.2.0 rc1 without a hitch and everything seemed to be working 
>> fine. I tried

Re: [wsjt-devel] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

2020-05-11 Thread lgtngstk

That is good to know thanks. I was going by the information included in the
tarball.

On Mon, May 11, 2020 at 6:49 PM Bill Somerville 
wrote:

> Hi OM,
>
> OK, thanks for the update. We recommend end users disable the manpages and
> documentation phase of the build, it is much easier to do that than it is
> to get the required packages installed.
>
> 73
> Bill
> G4WJS.
>
> On 11/05/2020 23:06, lgtngstk wrote:
>
> Ok I finally got it to finish. It really did not want to make the
> manpages. It was giving the a2x: ERROR: "xsltproc" error.
>
> On Mon, May 11, 2020 at 5:49 PM lgtngstk  wrote:
>
>> Attempting compile under a Ubuntu distro cmake says the following:
>> CMake Warning (dev) at CMakeLists.txt:165 (add_custom_target):
>>   Policy CMP0037 is not set: Target names should not be reserved and
>> should
>>   match a validity pattern.  Run "cmake --help-policy CMP0037" for policy
>>   details.  Use the cmake_policy command to set the policy and suppress
>> this
>>   warning.
>>
>>   The target name "install" is reserved or not valid for certain CMake
>>   features, such as generator expressions, and may result in undefined
>>   behavior.
>> This warning is for project developers.  Use -Wno-dev to suppress it.
>>
>> CMake Warning (dev) at CMakeLists.txt:166 (add_custom_target):
>>   Policy CMP0037 is not set: Target names should not be reserved and
>> should
>>   match a validity pattern.  Run "cmake --help-policy CMP0037" for policy
>>   details.  Use the cmake_policy command to set the policy and suppress
>> this
>>   warning.
>>
>>   The target name "package" is reserved or not valid for certain CMake
>>   features, such as generator expressions, and may result in undefined
>>   behavior.
>> This warning is for project developers.  Use -Wno-dev to suppress it.
>>
>> Which is fine since it does generate build files but later on the compile
>> fails with:
>>  [ 70%] Built target qcp
>> Makefile:149: recipe for target 'all' failed
>> make[3]: *** [all] Error 2
>> CMakeFiles/wsjtx-build.dir/build.make:60: recipe for target
>> 'wsjtx-prefix/src/wsjtx-stamp/wsjtx-build' failed
>> make[2]: *** [wsjtx-prefix/src/wsjtx-stamp/wsjtx-build] Error 2
>> CMakeFiles/Makefile2:324: recipe for target
>> 'CMakeFiles/wsjtx-build.dir/all' failed
>> make[1]: *** [CMakeFiles/wsjtx-build.dir/all] Error 2
>> Makefile:83: recipe for target 'all' failed
>> make: *** [all] Error 2
>>
>> I don't know weather these things are related.
>>
>
> ___
> 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] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

2020-05-11 Thread David Spoelstra

Thanks Bill. I might take a crack at building it...
-David, N9KT

On Mon, May 11, 2020 at 2:58 PM Bill Somerville 
wrote:

> Hi David,
>
> as noted on the WSJT-X web page
> https://physics.princeton.edu/pulsar/K1JT/wsjtx.html and in the README
> info on the project SourceForge files area
> https://sourceforge.net/projects/wsjt/files/wsjtx-2.2.0-rc1/ , the Debian
> style packages target Ubuntu 18.04. Although Ubuntu 20.04 is released there
> is no easy upgrade path for users until the 20.04.1 release in a couple of
> months, until then we will target the 18.04.x LTS release.
>
> The Ubuntu package maintainers for WSJT-X will probably make packages
> available soon that are suitable for various versions. In the meantime you
> can build WSJT-X from sources.
>
> 73
> Bill
> G4WJS.
>
> On 11/05/2020 19:21, David Spoelstra wrote:
>
> As a follow-on, I did install "gfortran": sudo apt install gfortran and
> got this:
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> gfortran is already the newest version (4:9.3.0-1ubuntu2).
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
> However I still get the error: "Depends: libgfortran3 (>= 4.8.2) but it is
> not installable" when I try and install wsjt-x
>
> Thanks!
> -David, N9KT
>
>
> On Mon, May 11, 2020 at 2:16 PM David Spoelstra 
> wrote:
>
>> When I tried to install in the latest Ubuntu 20.04 LTS, I got:
>> The following packages have unmet dependencies:
>>  wsjtx : Depends: libgfortran3 (>= 4.8.2) but it is not installable
>>
>> When I try "sudo apt install libgfortran3" I get:
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> E: Unable to locate package libgfortran3
>>
>> I'm a little lost as to how to get libgfortran3. Any suggestions?
>>
>> Thanks!
>> -David, N9KT
>>
>>
> ___
> 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] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

2020-05-11 Thread David Spoelstra

Sorry, forgot to mention that I tried "sudo apt install libgfortran3". No
joy. "Unable to locate package libgfortran3"


On Mon, May 11, 2020 at 2:56 PM Tag Loomis (Tag) 
wrote:

> Try:
>
> sudo apt install libgfortran3
>
> On Mon, May 11, 2020 at 11:53 AM David Spoelstra 
> wrote:
>
>> As a follow-on, I did install "gfortran": sudo apt install gfortran and
>> got this:
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> gfortran is already the newest version (4:9.3.0-1ubuntu2).
>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>>
>> However I still get the error: "Depends: libgfortran3 (>= 4.8.2) but it
>> is not installable" when I try and install wsjt-x
>>
>> Thanks!
>> -David, N9KT
>>
>>
>> On Mon, May 11, 2020 at 2:16 PM David Spoelstra 
>> wrote:
>>
>>> When I tried to install in the latest Ubuntu 20.04 LTS, I got:
>>> The following packages have unmet dependencies:
>>>  wsjtx : Depends: libgfortran3 (>= 4.8.2) but it is not installable
>>>
>>> When I try "sudo apt install libgfortran3" I get:
>>> Reading package lists... Done
>>> Building dependency tree
>>> Reading state information... Done
>>> E: Unable to locate package libgfortran3
>>>
>>> I'm a little lost as to how to get libgfortran3. Any suggestions?
>>>
>>> Thanks!
>>> -David, N9KT
>>>
>>> ___
>> 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] v2.2.0 rc1 Dropdown Frequency list anomaly

2020-05-11 Thread Greg Vatt

Mike,

At my first attempt to avoid writing a long email and not give every single 
detail it appears I didn’t communicate my point well. What I experienced, 
first, did not occur in the prior versions of WSJT-X and second, it exposes a 
potential underlying difference (maybe problem?) with how the code might be 
handling the drop down frequency list now. 

Observation:

After I change the frequency for the first time it appears the software never 
completely releases the action after the popup completes the original frequency 
change. The Frequency drop down remains active even after the list is collapsed 
(probably because it is both a drop down list and an editable text field). If I 
happen to pass the mouse over the frequency box again (no mouse down - no 
frequency list exposed) it can trigger a spontaneous repeating of the software 
to reconfigure the radio (multiple times on different frequencies in rapid 
fashion) until I get the popup with the Rig Control Error message. The recovery 
mode is then to select cancel which force quits WSJT-X and then reboot again. I 
only discovered the odd scrolling behavior when I tried to stop the action by 
forcing the drop down list to be exposed again and then select any frequency to 
stop it. Every once in a while it stops everything at that point before the Rig 
Control Error message comes up.

Observation:

If I resume operation after a successful frequency change without clicking on 
any other text field or control on the WSJT-X page both the mouse-scroll and 
the keyboard up/down keys can still cause the frequency to change even though 
the Frequency drop down list is no longer exposed (maybe desired - but not the 
same behavior on a Mac as V2.1.2 - see below). If I select some other text 
field in the window then only the up/down keys are disabled from making a 
frequency change from that point on but the scroll of the Frequency List (now 
hidden) still is operational if the mouse ventures into the Frequency control 
field again. (Doesn’t matter if the cursor is blinking and active in the 
Frequency Edit Field or blinking somewhere else on the page.)

(The behavior is the same for the up/down keys in V2.1.2, but V2.1.2 has the 
mouse scroll disabled on
a Mac for all conditions regarding frequency selection except when the 
Frequency List is exposed.)

I’m hoping to communicate that one would think the new Frequency selection 
would be determined when the Frequency selection list is opened on the first 
mouse-click and then the new frequency choice is finalized on the second 
mouse-click (when the list is collapsed again) no matter if the selection is 
made by scrolling to the frequency choice or using the up/down keys. All of 
these strange behaviors I’m experiencing can occur without the drop down list 
ever being exposed. If the scrolling action can cause bad things to happen then 
it shouldn’t be allowed in the code loop until after a drop down occurs (that 
was the V2.1.2 behavior on a Mac).

On a Mac, the WSJT-X frequency selection is a single-finger, one-step, 
no-mouse-move process, when using a Multi-Touch surface mouse. It becomes a 
multi-step move and mouse click process when the up/down keys are involved. So, 
I am just trying to take advantage of the simplified process that always worked 
before. 

Summary:

I’m just trying to report new observations that did not happen to me with the 
prior versions of WSJT-X while using my same operational pattern. This one 
potentially could cause problems if it occurred during a QSO an a rig 
reconfiguration was accidentally triggered. 

To end on a positive note, Thanks to the team for the hard work and overall 
great product!  This new version is working great when I’m actually in a QSO 
(and I keep my mouse away from the Frequency Selection area of the screen)!

Greg  NC7B

> On May 11, 2020, at 1:06 PM, Black Michael via wsjt-devel 
>  wrote:
> 
> Patient says...doc...it hurts when I do thisdoctor says...then don't do 
> that.
> 
> What your doing is asking the list to scroll which changes the band which 
> tells your rig to change bands.  You can do the same thing with the cursor 
> up/down keys.
> 
> So don't do that.
> 
> de Mike W9MDB
> 
> 
> 
> 
> On Monday, May 11, 2020, 12:18:59 PM CDT, Greg Vatt  wrote:
> 
> 
> Bill,
> 
> I downloaded v2.2.0 rc1 without a hitch and everything seemed to be working 
> fine. I tried it out on the air and quickly had a successful QSO. Then I went 
> to change bands and that’s when something strange happened.
> 
> I went to the dropdown list to change the frequency and the frequencies 
> appeared as they should. I have a number of frequencies so sometimes it is 
> necessary to scroll up or down depending on where I currently am in the list. 
> It worked OK the first time. However, if I tried to be too quick, by doing a 
> mouse-down and mouse-move in rapid succession, WSJT-x started commanding my 
> IC-7610 to reconfigure multiple times a second, jumping

Re: [wsjt-devel] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

2020-05-11 Thread Bill Somerville


Hi OM,

OK, thanks for the update. We recommend end users disable the manpages 
and documentation phase of the build, it is much easier to do that than 
it is to get the required packages installed.


73
Bill
G4WJS.

On 11/05/2020 23:06, lgtngstk wrote:
Ok I finally got it to finish. It really did not want to make the 
manpages. It was giving the a2x: ERROR: "xsltproc" error.


On Mon, May 11, 2020 at 5:49 PM lgtngstk > wrote:


Attempting compile under a Ubuntu distro cmake says the following:
CMake Warning (dev) at CMakeLists.txt:165 (add_custom_target):
  Policy CMP0037 is not set: Target names should not be reserved
and should
  match a validity pattern.  Run "cmake --help-policy CMP0037" for
policy
  details.  Use the cmake_policy command to set the policy and
suppress this
  warning.

  The target name "install" is reserved or not valid for certain CMake
  features, such as generator expressions, and may result in undefined
  behavior.
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at CMakeLists.txt:166 (add_custom_target):
  Policy CMP0037 is not set: Target names should not be reserved
and should
  match a validity pattern.  Run "cmake --help-policy CMP0037" for
policy
  details.  Use the cmake_policy command to set the policy and
suppress this
  warning.

  The target name "package" is reserved or not valid for certain CMake
  features, such as generator expressions, and may result in undefined
  behavior.
This warning is for project developers.  Use -Wno-dev to suppress it.

Which is fine since it does generate build files but later on the
compile fails with:
 [ 70%] Built target qcp
Makefile:149: recipe for target 'all' failed
make[3]: *** [all] Error 2
CMakeFiles/wsjtx-build.dir/build.make:60: recipe for target
'wsjtx-prefix/src/wsjtx-stamp/wsjtx-build' failed
make[2]: *** [wsjtx-prefix/src/wsjtx-stamp/wsjtx-build] Error 2
CMakeFiles/Makefile2:324: recipe for target
'CMakeFiles/wsjtx-build.dir/all' failed
make[1]: *** [CMakeFiles/wsjtx-build.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2

I don't know weather these things are related.



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

Re: [wsjt-devel] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

2020-05-11 Thread lgtngstk

Ok I finally got it to finish. It really did not want to make the manpages.
It was giving the a2x: ERROR: "xsltproc" error.

On Mon, May 11, 2020 at 5:49 PM lgtngstk  wrote:

> Attempting compile under a Ubuntu distro cmake says the following:
> CMake Warning (dev) at CMakeLists.txt:165 (add_custom_target):
>   Policy CMP0037 is not set: Target names should not be reserved and should
>   match a validity pattern.  Run "cmake --help-policy CMP0037" for policy
>   details.  Use the cmake_policy command to set the policy and suppress
> this
>   warning.
>
>   The target name "install" is reserved or not valid for certain CMake
>   features, such as generator expressions, and may result in undefined
>   behavior.
> This warning is for project developers.  Use -Wno-dev to suppress it.
>
> CMake Warning (dev) at CMakeLists.txt:166 (add_custom_target):
>   Policy CMP0037 is not set: Target names should not be reserved and should
>   match a validity pattern.  Run "cmake --help-policy CMP0037" for policy
>   details.  Use the cmake_policy command to set the policy and suppress
> this
>   warning.
>
>   The target name "package" is reserved or not valid for certain CMake
>   features, such as generator expressions, and may result in undefined
>   behavior.
> This warning is for project developers.  Use -Wno-dev to suppress it.
>
> Which is fine since it does generate build files but later on the compile
> fails with:
>  [ 70%] Built target qcp
> Makefile:149: recipe for target 'all' failed
> make[3]: *** [all] Error 2
> CMakeFiles/wsjtx-build.dir/build.make:60: recipe for target
> 'wsjtx-prefix/src/wsjtx-stamp/wsjtx-build' failed
> make[2]: *** [wsjtx-prefix/src/wsjtx-stamp/wsjtx-build] Error 2
> CMakeFiles/Makefile2:324: recipe for target
> 'CMakeFiles/wsjtx-build.dir/all' failed
> make[1]: *** [CMakeFiles/wsjtx-build.dir/all] Error 2
> Makefile:83: recipe for target 'all' failed
> make: *** [all] Error 2
>
> I don't know weather these things are related.
>
> On Mon, May 11, 2020 at 3:04 PM Bill Somerville 
> wrote:
>
>> Hi David,
>>
>> as noted on the WSJT-X web page
>> https://physics.princeton.edu/pulsar/K1JT/wsjtx.html and in the README
>> info on the project SourceForge files area
>> https://sourceforge.net/projects/wsjt/files/wsjtx-2.2.0-rc1/ , the
>> Debian style packages target Ubuntu 18.04. Although Ubuntu 20.04 is
>> released there is no easy upgrade path for users until the 20.04.1 release
>> in a couple of months, until then we will target the 18.04.x LTS release.
>>
>> The Ubuntu package maintainers for WSJT-X will probably make packages
>> available soon that are suitable for various versions. In the meantime you
>> can build WSJT-X from sources.
>>
>> 73
>> Bill
>> G4WJS.
>>
>> On 11/05/2020 19:21, David Spoelstra wrote:
>>
>> As a follow-on, I did install "gfortran": sudo apt install gfortran and
>> got this:
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> gfortran is already the newest version (4:9.3.0-1ubuntu2).
>> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>>
>> However I still get the error: "Depends: libgfortran3 (>= 4.8.2) but it
>> is not installable" when I try and install wsjt-x
>>
>> Thanks!
>> -David, N9KT
>>
>>
>> On Mon, May 11, 2020 at 2:16 PM David Spoelstra 
>> wrote:
>>
>>> When I tried to install in the latest Ubuntu 20.04 LTS, I got:
>>> The following packages have unmet dependencies:
>>>  wsjtx : Depends: libgfortran3 (>= 4.8.2) but it is not installable
>>>
>>> When I try "sudo apt install libgfortran3" I get:
>>> Reading package lists... Done
>>> Building dependency tree
>>> Reading state information... Done
>>> E: Unable to locate package libgfortran3
>>>
>>> I'm a little lost as to how to get libgfortran3. Any suggestions?
>>>
>>> Thanks!
>>> -David, N9KT
>>>
>>>
>> ___
>> 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] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

2020-05-11 Thread lgtngstk

Attempting compile under a Ubuntu distro cmake says the following:
CMake Warning (dev) at CMakeLists.txt:165 (add_custom_target):
  Policy CMP0037 is not set: Target names should not be reserved and should
  match a validity pattern.  Run "cmake --help-policy CMP0037" for policy
  details.  Use the cmake_policy command to set the policy and suppress this
  warning.

  The target name "install" is reserved or not valid for certain CMake
  features, such as generator expressions, and may result in undefined
  behavior.
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at CMakeLists.txt:166 (add_custom_target):
  Policy CMP0037 is not set: Target names should not be reserved and should
  match a validity pattern.  Run "cmake --help-policy CMP0037" for policy
  details.  Use the cmake_policy command to set the policy and suppress this
  warning.

  The target name "package" is reserved or not valid for certain CMake
  features, such as generator expressions, and may result in undefined
  behavior.
This warning is for project developers.  Use -Wno-dev to suppress it.

Which is fine since it does generate build files but later on the compile
fails with:
 [ 70%] Built target qcp
Makefile:149: recipe for target 'all' failed
make[3]: *** [all] Error 2
CMakeFiles/wsjtx-build.dir/build.make:60: recipe for target
'wsjtx-prefix/src/wsjtx-stamp/wsjtx-build' failed
make[2]: *** [wsjtx-prefix/src/wsjtx-stamp/wsjtx-build] Error 2
CMakeFiles/Makefile2:324: recipe for target
'CMakeFiles/wsjtx-build.dir/all' failed
make[1]: *** [CMakeFiles/wsjtx-build.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2

I don't know weather these things are related.

On Mon, May 11, 2020 at 3:04 PM Bill Somerville 
wrote:

> Hi David,
>
> as noted on the WSJT-X web page
> https://physics.princeton.edu/pulsar/K1JT/wsjtx.html and in the README
> info on the project SourceForge files area
> https://sourceforge.net/projects/wsjt/files/wsjtx-2.2.0-rc1/ , the Debian
> style packages target Ubuntu 18.04. Although Ubuntu 20.04 is released there
> is no easy upgrade path for users until the 20.04.1 release in a couple of
> months, until then we will target the 18.04.x LTS release.
>
> The Ubuntu package maintainers for WSJT-X will probably make packages
> available soon that are suitable for various versions. In the meantime you
> can build WSJT-X from sources.
>
> 73
> Bill
> G4WJS.
>
> On 11/05/2020 19:21, David Spoelstra wrote:
>
> As a follow-on, I did install "gfortran": sudo apt install gfortran and
> got this:
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> gfortran is already the newest version (4:9.3.0-1ubuntu2).
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
> However I still get the error: "Depends: libgfortran3 (>= 4.8.2) but it is
> not installable" when I try and install wsjt-x
>
> Thanks!
> -David, N9KT
>
>
> On Mon, May 11, 2020 at 2:16 PM David Spoelstra 
> wrote:
>
>> When I tried to install in the latest Ubuntu 20.04 LTS, I got:
>> The following packages have unmet dependencies:
>>  wsjtx : Depends: libgfortran3 (>= 4.8.2) but it is not installable
>>
>> When I try "sudo apt install libgfortran3" I get:
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> E: Unable to locate package libgfortran3
>>
>> I'm a little lost as to how to get libgfortran3. Any suggestions?
>>
>> Thanks!
>> -David, N9KT
>>
>>
> ___
> 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] WSJT-X 2.2.0-rc1 Crash on Mac

2020-05-11 Thread Chuck Reti WV8A via wsjt-devel

FYI I can change the displayed fonts by editing the typeface or size info in 
the .ini file, and can also switch to configurations that have different font 
settings. Getting the crash only when clicking the Font button(s) in the 
Preferences>General pane.

Chuck
WV8A

> On May 11, 2020, at 5:38 PM, George J Molnar  wrote:
> 
> Unable to duplicate on 10.15.5 (beta). Fonts changed as expected.
> 
> George J Molnar, KF2T 
> Arlington, Virginia, USA

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

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 Crash on Mac

2020-05-11 Thread George J Molnar

Unable to duplicate on 10.15.5 (beta). Fonts changed as expected.

George J Molnar, KF2T 
Arlington, Virginia, USA


> On May 11, 2020, at 5:08 PM, Chuck Reti WV8A via wsjt-devel 
>  wrote:
> 
> 
> Bill,
> 
> Deleted Font and DecodedTextFont lines from the .ini file for my “default” 
> FT8 Config, (though noticing that every one of the configs has its own Font 
> settings lines)
> Still crashing when ticking the font buttons in settings.
> 
> pasted below is additional info from Terminal. Sent this earlier but 
> Sourceforge bounced mail via my VPN’s IP.
> ——
> 
> /Applications/wsjtx.app/Contents/MacOS/wsjtx ; exit;
> qt.qpa.fonts: Populating font family aliases took 1142 ms. Replace uses of 
> missing font family "MS Shell Dlg 2" with one that exists to avoid this cost. 
> qt.qpa.fonts: QCoreTextFontDatabase: Found no matching fonts for family ""
> qt.qpa.fonts: QCoreTextFontDatabase: Found no matching fonts for family ""
> Segmentation fault: 11
> logout
> Saving session...
> ...copying shared history...
> ...saving history...truncating history files...
> ...completed.
> Deleting expired sessions...none found.
> 
> [Process completed]
> 
> — 
> 
> Chuck
> WV8A
> 
> 
> ___
> 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] WSJT-X 2.2.0-rc1 Crash on Mac

2020-05-11 Thread Chuck Reti WV8A via wsjt-devel

Bill,

Deleted Font and DecodedTextFont lines from the .ini file for my “default” FT8 
Config, (though noticing that every one of the configs has its own Font 
settings lines)
Still crashing when ticking the font buttons in settings.

pasted below is additional info from Terminal. Sent this earlier but 
Sourceforge bounced mail via my VPN’s IP.
——

/Applications/wsjtx.app/Contents/MacOS/wsjtx ; exit;
qt.qpa.fonts: Populating font family aliases took 1142 ms. Replace uses of 
missing font family "MS Shell Dlg 2" with one that exists to avoid this cost. 
qt.qpa.fonts: QCoreTextFontDatabase: Found no matching fonts for family ""
qt.qpa.fonts: QCoreTextFontDatabase: Found no matching fonts for family ""
Segmentation fault: 11
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
Deleting expired sessions...none found.

[Process completed]

— 

Chuck
WV8A


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

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 Crash on Mac

2020-05-11 Thread Bill Somerville


On 11/05/2020 20:32, Chuck Reti WV8A via wsjt-devel wrote:

macOS Mojave 10.14.6 MacBook Pro 13,3 15” 2016.
Installed rc1, TX,OK, RX decodes OK.
Preferences>General- simply clicking either the Font or Decoded Text Font 
buttons causes an immediate crash.
Repeated a number of times with same result. Report attached.

Chuck
WV8A


Hi Chuck,

that looks like a defect in the Qt get font dialog. I've searched for a 
Qt bug report on that but can't find one so it may be unreported. I 
can't reproduce the crash on my 10.14.3 macOS VM. Before I raise an 
issue with the Qt team can you try deleting the font lines from the 
WSJT-X settings file and see it that helps. The file is:


~/Library/Preferences/WSJT-X.ini

and can be edited in any text editor, e.g. TextEdit. Delete the lines 
starting as follows:


Font=

and

DecodedTextFont=

save the file and try starting WSJT-X again then adjusting the fonts.

73
Bill
G4WJS.



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

[wsjt-devel] WSJT-X 2.2.0-rc1 Crash on Mac

2020-05-11 Thread Chuck Reti WV8A via wsjt-devel

macOS Mojave 10.14.6 MacBook Pro 13,3 15” 2016.
Installed rc1, TX,OK, RX decodes OK.
Preferences>General- simply clicking either the Font or Decoded Text Font 
buttons causes an immediate crash.
Repeated a number of times with same result. Report attached.

Chuck
WV8A
Process:   wsjtx [8455]
Path:  /Applications/wsjtx.app/Contents/MacOS/wsjtx
Identifier:org.k1jt.wsjtx
Version:   v2.2.0-rc1 (2.2.0-rc1)
Code Type: X86-64 (Native)
Parent Process:??? [1]
Responsible:   wsjtx [8455]
User ID:   502

Date/Time: 2020-05-11 14:38:22.005 -0400
OS Version:Mac OS X 10.14.6 (18G4032)
Report Version:12
Bridge OS Version: 3.0 (14Y908)
Anonymous UUID:4C973C77-03F1-C8B5-E275-3FE4F57BDCBA

Sleep/Wake UUID:   113E9809-BA93-45D0-9E19-9AFDFD3A9E0D

Time Awake Since Boot: 66000 seconds
Time Since Wake:   4800 seconds

System Integrity Protection: enabled

Crashed Thread:0  Dispatch queue: com.apple.main-thread

Exception Type:EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:   KERN_INVALID_ADDRESS at 0x
Exception Note:EXC_CORPSE_NOTIFY

Termination Signal:Segmentation fault: 11
Termination Reason:Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [8455]

VM Regions Near 0:
--> 
__TEXT 0001005ff000-000100b73000 [ 5584K] r-x/rwx 
SM=COW  /Applications/wsjtx.app/Contents/MacOS/wsjtx

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   org.qt-project.QtGui0x0001058a792b 
bestStyle(QtFontFoundry*, QtFontStyle::Key const&, QString const&) + 411
1   org.qt-project.QtGui0x0001058a7573 
QFontDatabase::font(QString const&, QString const&, int) const + 547
2   org.qt-project.QtWidgets0x0001050f6b23 
QFontDialogPrivate::_q_updateSample() + 163
3   org.qt-project.QtWidgets0x0001050f6a70 
QFontDialogPrivate::updateSizes() + 1072
4   org.qt-project.QtWidgets0x0001050f648e 
QFontDialogPrivate::updateStyles() + 1150
5   org.qt-project.QtWidgets0x0001050f6e5e 
QFontDialogPrivate::_q_familyHighlighted(int) + 190
6   org.qt-project.QtCore   0x000106038bd5 void 
doActivate(QObject*, int, void**) + 1477
7   org.qt-project.QtWidgets0x0001050f7f7f 
QFontListView::currentChanged(QModelIndex const&, QModelIndex const&) + 95
8   org.qt-project.QtCore   0x000106038bd5 void 
doActivate(QObject*, int, void**) + 1477
9   org.qt-project.QtCore   0x000105fc8329 
QItemSelectionModel::setCurrentIndex(QModelIndex const&, 
QFlags) + 249
10  org.qt-project.QtWidgets0x00010512bac5 
QAbstractItemView::setCurrentIndex(QModelIndex const&) + 149
11  org.qt-project.QtWidgets0x0001050f542c 
QFontDialogPrivate::updateFamilies() + 1180
12  org.qt-project.QtWidgets0x0001050f4905 
QFontDialogPrivate::init() + 1957
13  org.qt-project.QtWidgets0x0001050f5a4d 
QFontDialogPrivate::getFont(bool*, QFont const&, QWidget*, QString const&, 
QFlags) + 45
14  org.qt-project.QtWidgets0x0001050f5a0e 
QFontDialog::getFont(bool*, QFont const&, QWidget*, QString const&, 
QFlags) + 14
15  org.k1jt.wsjtx  0x0001006db946 
Configuration::impl::on_font_push_button_clicked() + 54
16  org.k1jt.wsjtx  0x0001006dd68c 
Configuration::impl::qt_metacall(QMetaObject::Call, int, void**) + 76
17  org.qt-project.QtCore   0x000106038a6e void 
doActivate(QObject*, int, void**) + 1118
18  org.qt-project.QtWidgets0x000104fac71f 
QAbstractButtonPrivate::emitClicked() + 111
19  org.qt-project.QtWidgets0x000104fac5b9 
QAbstractButtonPrivate::click() + 233
20  org.qt-project.QtWidgets0x000104fad6ef 
QAbstractButton::mouseReleaseEvent(QMouseEvent*) + 271
21  org.qt-project.QtWidgets0x000104efd99d 
QWidget::event(QEvent*) + 445
22  org.qt-project.QtWidgets0x000104ec2f5a 
QApplicationPrivate::notify_helper(QObject*, QEvent*) + 266
23  org.qt-project.QtWidgets0x000104ec5e32 
QApplication::notify(QObject*, QEvent*) + 7330
24  org.k1jt.wsjtx  0x0001007150c2 (anonymous 
namespace)::ExceptionCatchingApplication::notify(QObject*, QEvent*) + 18
25  org.qt-project.QtCore   0x0001060059f4 
QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212
26  org.qt-project.QtWidgets0x000104ec3880 
QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, 
QWidget**, QPointer&, bool, bool) + 896
27  org.qt-project.QtWidgets0x000104f1c908 
QWidgetWindow::handleMouseEvent(QMouseEvent*) + 1704
28  org.qt-project.QtWidgets0x000104f1b5f5 
QWidgetWindow::event(QEvent*) + 229
29

[wsjt-devel] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

2020-05-11 Thread David Spoelstra

When I tried to install in the latest Ubuntu 20.04 LTS, I got:
The following packages have unmet dependencies:
 wsjtx : Depends: libgfortran3 (>= 4.8.2) but it is not installable

When I try "sudo apt install libgfortran3" I get:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package libgfortran3

I'm a little lost as to how to get libgfortran3. Any suggestions?

Thanks!
-David, N9KT
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

2020-05-11 Thread Jim Jennings

Noticed that a few versions ago.  To get rid of the “residue” in Settings>Apps 
I reinstalled, then uninstalled, the old versions appearing there.  Now, for 
each installation I append the version number to the default “WSJT-X” to have 
the installer create a new subdirectory for the destination.

73,

Jim, W7XZ

From: Black Michael via wsjt-devel 
Sent: Monday, May 11, 2020 10:51
To: WSJT software development 
Cc: Black Michael 
Subject: Re: [wsjt-devel] WSJT-X 2.2.0-rc1

Unless something changed failing to uninstall the old version leaves programs 
hanging around in the Windows uninstall arena that can't be uninstalled.

I also noticed that Communications is mispelled Communicaitions.

de Mike W9MDB






On Monday, May 11, 2020, 09:48:02 AM CDT, Joe Taylor  
wrote: 


WSJT-X 2.2.0 will be a significant program upgrade offering many new 

features.


The first candidate release, WSJT-X 2.2.0-rc1, is now available for 

download and use by beta testers.  This candidate release is your first 

chance to test the new features and provide feedback to the WSJT 

Development Group.


A list of program changes since WSJT-X 2.1.2 can be found in the 

cumulative Release Notes

http://physics.princeton.edu/pulsar/k1jt/Release_Notes.txt

... and also in the updated WSJT-X 2.2.0 User Guide here:

http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.0-rc1.html#NEW_FEATURES


Upgrading from earlier versions of WSJT-X should be seamless.  There is 

no need to uninstall a previous version or move any files.  You might 

want to install to a different directory from your WSJT-X 2.1.2 

installation.


Links to installation packages for Windows, Linux, and Macintosh are 

available here:

http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

Scroll down to find "Candidate release:  WSJT-X 2.2.0-rc1".


You can also download the packages from our SourceForge site:

https://sourceforge.net/projects/wsjt/files/

It may take a short time for the SourceForge site to be updated.


WSJT-X is licensed under the terms of Version 3 of the GNU General 

Public License (GPL).  Development of this software is a cooperative 

project to which many amateur radio operators have contributed.  If you 

use our code, please have the courtesy to let us know about it.  If you 

find bugs or make improvements to the code, please report them to us in 

a timely fashion.


We hope you will enjoy using this beta release of WSJT-X 2.2.0.  Please 

report bugs by following instructions found here in the User Guide:

http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.0-rc1.html#_bug_reports


  -- 73 from Joe, K1JT, Steve, K9AN, and Bill, G4WJS, for the

WSJT Development Group



___

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] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

2020-05-11 Thread Bill Somerville


Hi David,

as noted on the WSJT-X web page 
https://physics.princeton.edu/pulsar/K1JT/wsjtx.html and in the README 
info on the project SourceForge files area 
https://sourceforge.net/projects/wsjt/files/wsjtx-2.2.0-rc1/ , the 
Debian style packages target Ubuntu 18.04. Although Ubuntu 20.04 is 
released there is no easy upgrade path for users until the 20.04.1 
release in a couple of months, until then we will target the 18.04.x LTS 
release.


The Ubuntu package maintainers for WSJT-X will probably make packages 
available soon that are suitable for various versions. In the meantime 
you can build WSJT-X from sources.


73
Bill
G4WJS.

On 11/05/2020 19:21, David Spoelstra wrote:
As a follow-on, I did install "gfortran": sudo apt install gfortran 
and got this:

Reading package lists... Done
Building dependency tree
Reading state information... Done
gfortran is already the newest version (4:9.3.0-1ubuntu2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

However I still get the error: "Depends: libgfortran3 (>= 4.8.2) but 
it is not installable" when I try and install wsjt-x


Thanks!
-David, N9KT


On Mon, May 11, 2020 at 2:16 PM David Spoelstra 
mailto:dav...@mediamachine.com>> wrote:


When I tried to install in the latest Ubuntu 20.04 LTS, I got:
The following packages have unmet dependencies:
 wsjtx : Depends: libgfortran3 (>= 4.8.2) but it is not installable

When I try "sudo apt install libgfortran3" I get:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package libgfortran3

I'm a little lost as to how to get libgfortran3. Any suggestions?

Thanks!
-David, N9KT



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

Re: [wsjt-devel] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

2020-05-11 Thread Tag Loomis (Tag)

Try:

sudo apt install libgfortran3

On Mon, May 11, 2020 at 11:53 AM David Spoelstra 
wrote:

> As a follow-on, I did install "gfortran": sudo apt install gfortran and
> got this:
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> gfortran is already the newest version (4:9.3.0-1ubuntu2).
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
> However I still get the error: "Depends: libgfortran3 (>= 4.8.2) but it is
> not installable" when I try and install wsjt-x
>
> Thanks!
> -David, N9KT
>
>
> On Mon, May 11, 2020 at 2:16 PM David Spoelstra 
> wrote:
>
>> When I tried to install in the latest Ubuntu 20.04 LTS, I got:
>> The following packages have unmet dependencies:
>>  wsjtx : Depends: libgfortran3 (>= 4.8.2) but it is not installable
>>
>> When I try "sudo apt install libgfortran3" I get:
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> E: Unable to locate package libgfortran3
>>
>> I'm a little lost as to how to get libgfortran3. Any suggestions?
>>
>> Thanks!
>> -David, N9KT
>>
>> ___
> 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] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

2020-05-11 Thread David Spoelstra

As a follow-on, I did install "gfortran": sudo apt install gfortran and got
this:
Reading package lists... Done
Building dependency tree
Reading state information... Done
gfortran is already the newest version (4:9.3.0-1ubuntu2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

However I still get the error: "Depends: libgfortran3 (>= 4.8.2) but it is
not installable" when I try and install wsjt-x

Thanks!
-David, N9KT

On Mon, May 11, 2020 at 2:16 PM David Spoelstra 
wrote:

> When I tried to install in the latest Ubuntu 20.04 LTS, I got:
> The following packages have unmet dependencies:
>  wsjtx : Depends: libgfortran3 (>= 4.8.2) but it is not installable
>
> When I try "sudo apt install libgfortran3" I get:
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> E: Unable to locate package libgfortran3
>
> I'm a little lost as to how to get libgfortran3. Any suggestions?
>
> Thanks!
> -David, N9KT
>
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X Translation

2020-05-11 Thread Joe Taylor


Hi Xavi,

We will be delighted to have your translation of the WSJT-X 2.2 User 
Guide into Catalan and Spanish.  Many thanks for your offer!


-- 73, Joe, K1JT

On 5/11/2020 13:45, Xavi Pérez wrote:

Hello all:

I'm Xavi Perez, EA3W and I offer you in case you want to do your good 
program in different languages.


I started doing translations for Twitter, Facebook, LoTW and now I did 
JTDX in Catalan, which is the language we speak in Catalonia. I can also 
do it in Spanish.


Since 2000, I have been president of Digigrup, the amateur radio club 
specialized in digital communications in Spain.


Greetings and thanks for your work, 73

Xavi Perez, EA3W

http://www.digigrup.org




Avast logo   

Aquest correu electrònic s'ha verificat mitjançant l'Avast antivirus.
www.avast.com 


<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>


___
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] WSJT-X Translation

2020-05-11 Thread Xavi Pérez



Hello all:

I'm Xavi Perez, EA3W and I offer you in case you want to do your good program 
in different languages.
I started doing translations for Twitter, Facebook, LoTW and now I did JTDX in 
Catalan, which is the language we speak in Catalonia. I can also do it in 
Spanish.

Since 2000, I have been president of Digigrup, the amateur radio club 
specialized in digital communications in Spain.

Greetings and thanks for your work, 73

Xavi Perez, EA3W
http://www.digigrup.org




--
Aquest correu electrònic s'ha verificat mitjançant l'Avast antivirus.
https://www.avast.com/antivirus
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

2020-05-11 Thread Black Michael via wsjt-devel

Unless something changed failing to uninstall the old version leaves programs 
hanging around in the Windows uninstall arena that can't be uninstalled.
I also noticed that Communications is mispelled Communicaitions.
de Mike W9MDB



 

On Monday, May 11, 2020, 09:48:02 AM CDT, Joe Taylor  
wrote:  
 
 WSJT-X 2.2.0 will be a significant program upgrade offering many new 
features.

The first candidate release, WSJT-X 2.2.0-rc1, is now available for 
download and use by beta testers.  This candidate release is your first 
chance to test the new features and provide feedback to the WSJT 
Development Group.

A list of program changes since WSJT-X 2.1.2 can be found in the 
cumulative Release Notes
http://physics.princeton.edu/pulsar/k1jt/Release_Notes.txt
... and also in the updated WSJT-X 2.2.0 User Guide here:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.0-rc1.html#NEW_FEATURES

Upgrading from earlier versions of WSJT-X should be seamless.  There is 
no need to uninstall a previous version or move any files.  You might 
want to install to a different directory from your WSJT-X 2.1.2 
installation.

Links to installation packages for Windows, Linux, and Macintosh are 
available here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
Scroll down to find "Candidate release:  WSJT-X 2.2.0-rc1".

You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/
It may take a short time for the SourceForge site to be updated.

WSJT-X is licensed under the terms of Version 3 of the GNU General 
Public License (GPL).  Development of this software is a cooperative 
project to which many amateur radio operators have contributed.  If you 
use our code, please have the courtesy to let us know about it.  If you 
find bugs or make improvements to the code, please report them to us in 
a timely fashion.

We hope you will enjoy using this beta release of WSJT-X 2.2.0.  Please 
report bugs by following instructions found here in the User Guide:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.0-rc1.html#_bug_reports

      -- 73 from Joe, K1JT, Steve, K9AN, and Bill, G4WJS, for the
                        WSJT Development Group


___
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] WSJT-X 2.2.0-rc1

2020-05-11 Thread Serge Smirnoff R6YY via wsjt-devel


Thanks Joe. You're great. 73


11.05.2020 17:44, Joe Taylor пишет:
WSJT-X 2.2.0 will be a significant program upgrade offering many new 
features. The first candidate release...



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

Re: [wsjt-devel] Interesting new Band Activity operation

2020-05-11 Thread Bill Somerville


On 11/05/2020 15:37, WB5JJJ wrote:
Just installed v2.2.0 rc1 and found that the Band Activity window has 
a "new normal" that I find awkward.


After the first decode period at 11.8s, the window works exactly as 
before, but at the conconsulsion of ALL decodes at ~15s, it resets the 
display to show only those last decoded.  You must scroll up to see 
the original (larger) list of decodes.


Temporary solution under Settings is to uncheck "Start new period 
decodes at top".  Now you have a continuous flow of decodes (old 
way).  I really enjoyed the start new decodes with the overflow off 
the bottom of the BA window, a much smaller list typically.  I have 
part of the monitor display real estate taken up  by JTAlert with just 
3 lines of decodes, docked above WSJTx.

--
George - WB5JJJ


Hi George,

thanks for the issue report, I can confirm that is a defect, and as you 
suggest the current workaround is to uncheck the 
"Settings->General->Start new decodes from top" option.


73
Bill
G4WJS.

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

[wsjt-devel] FYI ...

2020-05-11 Thread Neil Zampella


Hi all,

just a heads up that when I tried to run the setup of v2.2.0-RC1, AVG
did not recognize it as valid, and automatically submitted it to AVG for
analysis.   Once its analyzed AVG will allow installation.

Takes about 5 or 10 minutes but once done, won't happen again. Notice,
it did not just delete the file, and give a bunch of cryptic warnings

Neil, KN3ILZ


--
This email has been checked for viruses by AVG.
https://www.avg.com



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

[wsjt-devel] WSJT-X 2.2.0-rc1

2020-05-11 Thread Joe Taylor

WSJT-X 2.2.0 will be a significant program upgrade offering many new
features.

A list of program changes since WSJT-X 2.1.2 can be found in the
cumulative Release Notes

http://physics.princeton.edu/pulsar/k1jt/Release_Notes.txt
... and also in the updated WSJT-X 2.2.0 User Guide here:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.0-rc1.html#NEW_FEATURES

Links to installation packages for Windows, Linux, and Macintosh are
available here:

http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
Scroll down to find "Candidate release: WSJT-X 2.2.0-rc1".

You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/
It may take a short time for the SourceForge site to be updated.

We hope you will enjoy using this beta release of WSJT-X 2.2.0. Please
report bugs by following instructions found here in the User Guide:

http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.0-rc1.html#_bug_reports

-- 73 from Joe, K1JT, Steve, K9AN, and Bill, G4WJS, for the
WSJT Development Group

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

[wsjt-devel] Interesting new Band Activity operation

2020-05-11 Thread WB5JJJ

Just installed v2.2.0 rc1 and found that the Band Activity window has a
"new normal" that I find awkward.

After the first decode period at 11.8s, the window works exactly as before,
but at the conconsulsion of ALL decodes at ~15s, it resets the display to
show only those last decoded.  You must scroll up to see the original
(larger) list of decodes.

Temporary solution under Settings is to uncheck "Start new period decodes
at top".  Now you have a continuous flow of decodes (old way).  I really
enjoyed the start new decodes with the overflow off the bottom of the BA
window, a much smaller list typically.  I have part of the monitor display
real estate taken up  by JTAlert with just 3 lines of decodes, docked above
WSJTx.
-- 
George - WB5JJJ


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

Re: [wsjt-devel] Coming soon: WSJT-X 2.2.0-rc1

2020-05-11 Thread Stephen Ireland

Gents,

Smooth … Very smooth be the 2.2.0 rc1 from compilation under the Windows JTSDK 
3.1 with “master” Hamlib release and Qt 5.14.2

No deprecation or fall-through warnings … just the odd initialisation warning.

Very-very smooth gents. More than amazing !!! WELL DONE 

I thank all the core development team for this amazing effort !!!

73 and congratulations !

Steve I
VK3VM / VK3SIR

From: Stephen Ireland 
Sent: Monday, 11 May 2020 6:35 AM
To: WSJT software development 
Subject: Re: [wsjt-devel] Coming soon: WSJT-X 2.2.0-rc1

William,

Thanks for the response as it is highly appreciated not just by me but I am 
sure that the many asking these questions of me for guidance with appreciate 
your response.

Yes Qt 5.13 does have defects … and in my informed opinion MUST NOT BE USED! 
Yet the JTSDK is not mine to go tinkering with too heavily; all I do is provide 
guidance to and examples for many (frustrated others) that are keen to 
understand – keen to get The JTSDK 3.1 building code. Greg KI7MT does refer to 
5.13.0 – when some mirrored installer repositories across the planet only 
guarantee all versions of the LTS versions (all 5.12.x series) and the latest 
of the 5.13 and 5.14 series Qt SDK’s !

The decision for my educational “experimental” scripts to reference the master 
repositories was also based on suggestions received background from lots of 
sources. There are many hundreds of Amateurs and non-Amateurs alike that use 
the JTSDK not just for WSJT-X development …  SDK’s I believe should be 
standardised to “master” releases of libraries and support code. Just to 
compliment the HAMLIB developer team, I find that current “master” code 
provides infinitely better support for many common radios (i.e. the FT-991 that 
I use here).

Likewise software should always be standardised to “snapshotted” libraries and 
versions of those standard libraries. If one chooses to use later versions, 
then well and good  - but at their own risk and should expect grrr’s from 
support communities !

Some of the issues I have noted that frustrate many here in the “WSJT Software 
Developers” lists are related to people NOT using standard versions of 
packages; you and Joe have said almost tirelessly that standard versions of 
packages for developing “JT-mode code” on Windows are the JTSDK 3.0 and 3.1 . 
Work there has been static … and I have just provided some experimental 
resources to kick off other HAM’s learning processes.

I fully compliment you on, acknowledge, note and had already observed that your 
HAMLIB repository synchronises with the master repository…

With regards to the JTSDK I have stated repeatedly I do not want to tinker too 
much with Greg KI7MT’s work and add in new facilities… I loathe “forking” 
anyone’s repo unless it becomes extremely necessary (and I will NOT do it 
alone). Amateurs mostly are of age or have health issues; what happens if 
someone “falls off the perch”? Forking a project as we know creates minefields 
with referencing, acknowledgements etc. Putting my “experiments” into a 
GIT-pull is difficult (yet not insurmountable) as some replacement scripts need 
to be put into end-user MSYS2 home directories – names that are NOT 
standardised across User’s Windows Environs. Tricks and mess is what I am 
trying to avoid.

All new that I have added in is a “whome” DOSKEY to take you to the base of the 
C:\JTSDK64\tmp\wsjtx directory to assist with wsjtx and jtdx “git pull” 
commands. In my opinion that has even crossed the mark !!!

Based on your clear advisory here I may need to (reluctantly) demonstrate Greg 
KI7MT’s techniques and demonstrate a “build-hamlib.sh” script that searches for 
a “marker file” in the JTSDK profile directory for JTSDK 3.0 and 
“C:\JTSDK64-Tools\config” for JTSDK 3.1 that indicates whether Hamlib 
repositories are to be pulled from your GIT fork or from the master repository 
in a later “experiment” release – when time permits.

PLEASE do not take what I am about to say the wrong way as it is not an attack 
at your work or what you are doing  … really we only should be pulling key 
library code from one source as having mixtures of library code with slightly 
different interfaces can have long lasting and unforeseen consequences down the 
track (as we all have experienced in the past) !

I restate that my interest in this was sparked as I customise WSJT-X (and JTDX) 
for VERY disabled people that I work with; I also use the JTSDK for other 
projects that I work on. I am far from alone in using it this way.

Source, in my opinion, should not be released compliant with standardised 
“bastardised” sets of libraries - though a “reference” snapshot (provided with 
the source) at a particular point in time is always a great idea !
Code should always be maintained and compatible with the latest library 
enhancements; likewise libraries should never stray from core functions !

73 and again thanks. Keep up the amazing work !

Steve I
VK3VM / VK3SIR

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

Re: [wsjt-devel] Interesting new Band Activity operation

Re: [wsjt-devel] v2.2.0 rc1 Dropdown Frequency list anomaly

Re: [wsjt-devel] v2.2.0 rc1 Dropdown Frequency list anomaly

Re: [wsjt-devel] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

Re: [wsjt-devel] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

Re: [wsjt-devel] v2.2.0 rc1 Dropdown Frequency list anomaly

Re: [wsjt-devel] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

Re: [wsjt-devel] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

Re: [wsjt-devel] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

Re: [wsjt-devel] v2.2.0 rc1 Dropdown Frequency list anomaly

Re: [wsjt-devel] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

Re: [wsjt-devel] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

Re: [wsjt-devel] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 Crash on Mac

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 Crash on Mac

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 Crash on Mac

Re: [wsjt-devel] WSJT-X 2.2.0-rc1 Crash on Mac

[wsjt-devel] WSJT-X 2.2.0-rc1 Crash on Mac

[wsjt-devel] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

Re: [wsjt-devel] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

Re: [wsjt-devel] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

Re: [wsjt-devel] Installing WSJT-X 2.2.0-rc1 in Ubuntu 20.04 LTS doesn't work

Re: [wsjt-devel] WSJT-X Translation

[wsjt-devel] WSJT-X Translation

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

Re: [wsjt-devel] WSJT-X 2.2.0-rc1

Re: [wsjt-devel] Interesting new Band Activity operation

[wsjt-devel] FYI ...

[wsjt-devel] WSJT-X 2.2.0-rc1

[wsjt-devel] Interesting new Band Activity operation

Re: [wsjt-devel] Coming soon: WSJT-X 2.2.0-rc1

33 matches

Site Navigation

Mail list logo

Footer information