[wsjt-devel] compilation issue r8662

Hi Bill & All, Please consider the following out seen here, while trying to compile: [ 2%] Building CXX object CMakeFiles/wsjtx_udp-static.dir/Radio.cpp.o [ 3%] Building CXX object CMakeFiles/qcp.dir/qcustomplot-source/qcustomplot.cpp.o In file included from : ./wsjtx_config.h:47:11: error:

Re: [wsjt-devel] Fwd: WSJT-X Suggestion

Hi Jeff, Joe will have to address the question as to whether they would implement the feature. In the meantime, JT-Alerts is a “very useful” tool that will do what you are asking, and much more!! https://hamapps.com/ 73’s Greg, KI7MT From: k7xq [mailto:k...@elite.net]

Re: [wsjt-devel] Stations with bad clocks

> On 15 May 2018, at 18:16, Rich - K1HTV wrote: > If WSJT-X had a rubber clock feature which would temporarily speed up or slow > down the computer clock by a number of seconds, then a message could be sent > and decoded by those whose with inaccurate clocks. It doesn’t

Re: [wsjt-devel] Expeditionj & Standard Mode Enhancement Requests - from an expeditioner's perspective

Hi Grant, Thanks for your message of May 11, sharing your thoughts after operating as YJ0AG. It's good to hear that you achieved QSO rates as high as 50/hour using standard FT8 mode. You and others will be happy to know that a General Availability (GA) release of WSJT-X Version 1.9.0 is

Re: [wsjt-devel] WSJTX and Fedora 28

On 05/07/2018 11:35 AM, Bill Somerville wrote: Hi Bill & Jarmo, >> And when try compile in F28 I get: >> >> /wsjtx_config.h:47:11: virhe: ”size_t” ei nimeä tyyppiä >>     typedef size_t fortran_charlen_t; >>     ^~ >> ./wsjtx_config.h:47:11: huom: ”size_t” is defined in header >> ””;

Re: [wsjt-devel] Build environment macOS 10.13.4

Just a follow up, I got it to work with MacOSX SDK 10.13 Qt5-11-rc I had to update how the cmake file references the Qt modules. Everything else apart from the hamradio api was provided by homebrew and is more or less at the latest versions. It makes tones and decodes when I visit a websdr

Re: [wsjt-devel] WSJTX and Fedora 28

I haven't been following this thread in detail but we're not having any issues building the official Fedora packages, you may want to look there for some hints... https://src.fedoraproject.org/rpms/wsjtx Thanks, Richard KF5OIM

[wsjt-devel] Menus & Monitor // r8642

Generally, I run WSJT-X on my 2nd monitor. Since 6M is completely dead today, and I was bored, I decided to uncheck the "Menu" box, to see how much screen not having the menus would free up. Much to my surprise, WSJT-X jumped to Monitor #1, with

Re: [wsjt-devel] WSJTX and Fedora 28

On 05/16/2018 06:22 PM, Richard Shaw wrote: Hi Richard, Jarmo & All, > I haven't been following this thread in detail but we're not having any > issues building the official Fedora packages, you may want to look there > for some hints... > > https://src.fedoraproject.org/rpms/wsjtx I confess

Re: [wsjt-devel] WSJTX and Fedora 28

Hi! Just upgraded one laptop. Tried first to F28 but upgrade failed (missing 28 key). Then tried upgrade to F27 that went through, but how ever after reboot I had F28 anyway (!?!). Otherwise working, but locales damaged that needed some reinstall and locale generation. After that I also

Re: [wsjt-devel] Menus & Monitor // r8642

Not a bug..each windows has it's own memory settings so you just need to move it where you want it. de Mike W9MDB On Wednesday, May 16, 2018, 12:47:41 PM CDT, Steve Sacco NN4X wrote: Generally, I run WSJT-X on my 2nd monitor. Since 6M is completely dead

Re: [wsjt-devel] WSJTX and Fedora 28

On Wed, May 16, 2018 at 1:52 PM Saku wrote: > > How ever your link to src.fedoraproject has rpm that works. > > Just wondering what is the difference in gcc-gfortran, libgfortran and > libquadmath between "average user's F28" and rpm builder's F28 > Those seems to be the source

Re: [wsjt-devel] Menus & Monitor // r8642

Hi Steve, I don't know what you mean by "WSJT-X jumped to Monitor #1". If the Menu box is unchecked, the top-of window menus are not supposed to be displayed. So what was unexpected ?? --Joe, K1JT On 5/16/2018 1:45 PM, Steve Sacco NN4X wrote: Generally, I run WSJT-X on my 2nd

Re: [wsjt-devel] Build environment macOS 10.13.4

Hi Megan, I’m not sure I understand your meaning of switch to the appropriate branch. But in any case, WSJT (the original application) is Python based and resides in the Sourceforge trunk. WSJT-X resides in a branch of the trunk and is Qt5 based. If you are after a runnable-version for

Re: [wsjt-devel] Menus & Monitor // r8642

Hi Joe - The open WSJT-X application, which had been running in Monitor #2, moves itself to Monitor #1 the moment I uncheck the "Menus" box.  On Monitor #1, it is, as it should be, not displaying the menus. Re-checking the "Menus" box, WSJT-X

Re: [wsjt-devel] Build environment macOS 10.13.4

Hi Bill, Here is the diff. Index: CMakeLists.txt === --- CMakeLists.txt (revision 8662) +++ CMakeLists.txt (working copy) @@ -15,7 +15,7 @@ Earliest version we can support with Qt 5.8, C++11 & libc++ is 10.9. Do not override

Re: [wsjt-devel] Build environment macOS 10.13.4

On 16/05/2018 13:34, Megan Woods wrote: Just a follow up,  I got it to work with MacOSX SDK 10.13 Qt5-11-rc I had to update how the cmake file references the Qt modules. Hi Megan, what changes did you make to the CMake script? 73 Bill G4WJS.

Re: [wsjt-devel] Build environment macOS 10.13.4

One more thing Bill I am using the latest cmake. Megan On Thu, 17 May 2018 at 6:52 am, Megan Woods wrote: > Hi Bill, > > > Here is the diff. > > > > Index: CMakeLists.txt > === > --- CMakeLists.txt

[wsjt-devel] Fwd: WSJT-X Suggestion

Original message From: k7xq Date: 5/7/18 2:32 AM (GMT-08:00) To: wsjtgr...@yahoogroups.com Subject: WSJT-X Suggestion Hello,I am a current user of WSJT-X.  When using the program, stations not yet worked will show up in a purple background and

Re: [wsjt-devel] WSJTX and Fedora 28

On 05/16/2018 08:59 PM, Richard Shaw wrote: Hi Richard & All, > Just wondering what is the difference in gcc-gfortran, libgfortran and > libquadmath  between "average user's F28" and rpm builder's F28 > Those seems to be the source of this problem. > > > If I remember correctly the