TextEdit, a standard part of MacOS, did a fine job on my 50+MB 937492 line
ALL.TXT.
73 Bill AE6JV
On 6/1/20 at 5:00 PM, bob...@bellsouth.net (Bobby Chandler) wrote:
> Editpad Lite does an excellent job.
>
> Bobby/N4AU
---
Agreed. I just tested and it loaded a 10GB all.txt in seconds.
-Jim
NU0C
On Mon, 1 Jun 2020 12:20:02 -0700
"David Beauchesne" wrote:
> Jim,
>
> Notepad++ is much faster (and free).
>
> David, AK2L
>
>
> -Original Message-
> From: Jim Brown
> Sent: Monday, June 1, 2020 12:07
>
On 01/06/2020 23:36, Laurie, VK3AMA wrote:
Tracked down the JTAlert non-coloring of decodes in the release
candidates.
2.1.2 works correctly, but the -rcs don't (tested both rc2 & rc3) when
the decode string contains a positive report. Reports that are
negative are colored correctly.
eg.
Tracked down the JTAlert non-coloring of decodes in the release candidates.
2.1.2 works correctly, but the -rcs don't (tested both rc2 & rc3) when
the decode string contains a positive report. Reports that are negative
are colored correctly.
eg.
"AA1AA VK3AMA +12" & "AA1AA VK3AMA R+12" - FAIL
Files that large are difficult, not sure it should be allowed to get that
big? Maybe needs a routine to start a new one at suitable intervals, and
archive the previous one?
Alan G0TLK, sent from my mobile device
On 1 June 2020 21:18:57 Jim Shepherd wrote:
Ok, here is the section of the
Editpad Lite does an excellent job.
Bobby/N4AU
--
bob...@bellsouth.net
n...@arrl.net
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Ok, here is the section of the all.txt around the contact--I added the line
of * to make them easier to see. I was double clicking on stations
calling CW when the JH1LAT called me with the -11 signal report it did
not post to the logging window.
I agree with Jim Brown--Notepad
Jim,
Notepad++ is much faster (and free).
David, AK2L
-Original Message-
From: Jim Brown
Sent: Monday, June 1, 2020 12:07
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Recd signal report did not populate in log
On 6/1/2020 11:07 AM, Bill Somerville wrote:
> no need
On 6/1/2020 11:07 AM, Bill Somerville wrote:
no need for screen captures, all the relevant information should be in
your ALL.TXT file.
Hi Bill,
ALL.TXT brings Notepad to its knees, taking days to load. Can you
suggest a better viewer?
73, Jim K9YC
Hi Jim,
Check the All.txt file for that QSO to see what you actually decoded.
73,
Sam W2JDB
-Original Message-
From: Jim Shepherd
To: WSJT software development
Sent: Mon, Jun 1, 2020 2:03 pm
Subject: [wsjt-devel] Recd signal report did not populate in log
Hi This may just be a
On 01/06/2020 19:03, Jim Shepherd wrote:
Hi
This may just be a 'one-off' problem but it did occur in rc3.
A Japanese station answered my CQ with a "W6US JA1xxx -11" . I sent a
"JA1xxx W6US R-06". He came back with a RR73 and when my logger screen
popped up, the received -11 was not in the
Hi
This may just be a 'one-off' problem but it did occur in rc3.
A Japanese station answered my CQ with a "W6US JA1xxx -11" . I sent a
"JA1xxx W6US R-06". He came back with a RR73 and when my logger screen
popped up, the received -11 was not in the received signal report box... I
added the -11
Hi Dave,
As you note, the decodes counter displays the number of decodes found in
the most recent Rx sequence that produced any.
That was originally intended, but perhaps it is more useful to show zero
when none are found. The GA release will do so.
-- 73, Joe, K1JT
On 6/1/2020
Come to think of it likewise here on the counter, although graph situation
not checked so not seen.
Alan G0TLK, sent from my mobile device
On 1 June 2020 16:31:36 Dave Bernheisel via wsjt-devel
wrote:
I am using version 2.2.2-rc3 on windows 10 64 bit system.
I have noticed that the new
I am using version 2.2.2-rc3 on windows 10 64 bit system.
I have noticed that the new counter for number of decodes does not reset
for each interval. It appears to report the number of decodes during
the last interval for which there was a decode. Following an interval
in which there were
Hi Dave,
Sorry for the slow response to your kind offer to help with
documentation. Of course we will be delighted to accept any help you
can provide.
The WSJT-X User Guide uses the "asciidoc" markup language. Its source
files and images are maintained in the "git" version control system,
You apparently don't have the latest code.
This was fixed a couple days ago.
Mike W9MDB
On Monday, June 1, 2020, 01:27:18 AM CDT, Iztok Saje
wrote:
Hello!
Old slackware linux. Libraries needed for WSJTX had not been touched for some
two or three years.
When compiling hamlib, it
On 01/06/2020 07:22, Iztok Saje wrote:
Hello!
Old slackware linux. Libraries needed for WSJTX had not been touched
for some two or three years.
When compiling hamlib, it failed, because there is no git directory here.
I created tests/hamlibdatetime.h file with one line:
#define
Hello!
Old slackware linux. Libraries needed for WSJTX had not been touched for some
two or three years.
When compiling hamlib, it failed, because there is no git directory here.
I created tests/hamlibdatetime.h file with one line:
#define HAMLIBDATETIME "20200531"
and rerun make.
maybe
19 matches
Mail list logo
