Hi all ..
evidently r7887 is doubling the transmission entries when copying over
to the RX window. I remember this was an issue a few days before the
r7847 release of v1.8.0. Looks like it crept back in.
Neil, KN3ILZ
--
Rich,
It might be better for your visually-impaired friend to have someone develop a
'sister app' that interfaces with WSJT-X via the existing UDP interface. That
way any existing visual aides could be leveraged without having to add support
in the base application.
Just a thought.
On Jul 14,
On 15/07/2017 01:19, Bill Somerville wrote:
The ICE probably should be reported to the GCC team, that module is
third party to us (QCustomPlot) but it probably doesn't make a very
good test case as it is Qt code so not very standalone.
Having said that, it is all there since the preprocessor o
On 15/07/2017 00:55, Mike wrote:
Fedora always seems a cranky distro, GCC is 6.3.x and clang 3.8.x
cmake with gcc gave the errors below and switching to clang fails on the final
linking with forth omp.
gfortran is version 6.2.0.
No signal just noise.
-Mike.
Hi Mike,
thanks for that. Is it o
Fedora always seems a cranky distro, GCC is 6.3.x and clang 3.8.x
cmake with gcc gave the errors below and switching to clang fails on the final
linking with forth omp.
gfortran is version 6.2.0.
No signal just noise.
-Mike.
-- Found Subversion: /usr/bin/svn (found version "1.9.4")
[ 44%] Built
Joe and the WSJT-X software development team,
First, congrats on the superb job you all have done in the creation of the
new FT8 mode. It works great! In 5 days, while running 50 Watts, a triband yagi
and wire antenna, I've managed to work 62 countries using FT8, including some
nice catche
Hi Joe et all,
Just built wsjtx r7884 and am getting the following error after a few
seconds running. Win 10-64
Subprocess Error
Subprocess failed with exit code 3
Details:
Running: C:\WSJT\wsjtx\bin\jt9 -s WSJT-X -w 1 -m 3 -e C:\WSJT\wsjtx\bin
-a "C:\Users\Ron Gibson\AppData\Local\WSJT-X" -t
On 14/07/2017 18:53, Richard Shaw wrote:
procedure(timer_callback), pointer :: timer => null_timer
1
Error: Pointer initialization requires a NULL() at (1)
Hi Richard and David,
this one is this gfortran bug:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45290
which looks like it was
Here's the full log:
https://copr-be.cloud.fedoraproject.org/results/hobbes1069/WSJT/epel-6-x86_64/00579069-wsjtx/build.log.gz
But near the end you see this after I patch the CPPFLAGS to use c++0x
(rather than gnu++11)
There are two places where there appear to be serious errors:
/usr/bin/gfort
On 14/07/2017 17:29, David Ranch wrote:
From the compilation issues you saw for building the newest WSJT-X
code, do you think that some modification could be done to make it
more compatible with older GCC versions?
Hi David,
if you share the errors you are getting with gcc 4.4 I can probably
Hey Richard,
From the compilation issues you saw for building the newest WSJT-X
code, do you think that some modification could be done to make it more
compatible with older GCC versions?
--
$ gcc -v
Using built-in specs.
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr
The system is built around the auto sequencing. The only time you
really have to react with auto sequencing turned on, is when answering
a station calling CQ, or if you don't have "Call 1st" checks so you have
to double click on the person answering your CQ.
If you use the system as designed
FT8 (and other modes in WSJT) already support messages of the form
"CQ XX K1ABC FN42", where "XX" is any two letters. They have done so for some
considerable time. Obviously XX can be DX. So I do not understand what you are requesting.
Yes, but the grid square is not embedded in the call s
*Hi,**
** For me, 2 days of FT8 activities, many thanks to the developers.**
** I know that's a beta version so my suggest is have 20sec instead of
15sec.**
** Extra 5 sec make time to react and reply correctly ... Real VE2DSK*
---
I'd kindly suggest to include a table with all the modes affected by
the VHF/UHF/Microwave option
and what are the differences when VHF/UHF/Microwave is enabled / disabled.
There is a warning on page 9:
*"Enabling VHF/UHF/Microwave features necessarily disables the wideband
multidecode*
*capabili
On 7/14/2017 10:04 AM, Raymond Montagne wrote:
To whom it may concern,
The ARRL Letter instructed that suggestions for use of the 3 extra bits
in FT8 be sent to this list. Toward that end, would you please consider
using these bits for providing a CQ DX capability?
Thank you.
Best regards,
To whom it may concern,
The ARRL Letter instructed that suggestions for use of the 3 extra bits in FT8
be sent to this list. Toward that end, would you please consider using these
bits for providing a CQ DX capability?
Thank you.
Best regards, Ray Montagne (W7CIA)-
To whom it may concern,
The ARRL Letter instructed that suggestions for use of the 3 extra bits in FT8
be sent to this list. Toward that end, would you please consider using these
bits for providing a CQ DX capability?
Thank you.
Best regards, Ray Montagne (W7CIA)-
To whom it may concern,
The ARRL Letter instructed that suggestions for use of the 3 extra bits in FT8
be sent to this list. Toward that end, would you please consider using these
bits for providing a CQ DX capability?
Thank you.
Best regards, Ray Montagne (W7CIA)-
19 matches
Mail list logo
