Well ... the 73 is what triggers the WSJT-X log panel. As far as the
multiple RRR/RR73s, the RRR users send DO expect a 73 from you (at least
the system does), the RR73 users have no clue.
Neil, KN3ILZ
On 5/21/2020 6:17 PM, Al Pawlowski wrote:
Actually, just discovered that WSKJTx already
Hi All:
In ISCAT mode, if one double-clicks a message in the left hand RX signals pane
this presents a dialog box “Double clicking is not supported in ISCAT mode”.
When this dialog box is dismissed, the app crashes.
I am running rc1 on MacOS version 10.14.6 Mojave.
If you need further info
Hi Kevin,
On 5/22/2020 10:45 AM, Kevin McQuiggin VE7ZD/KN7Q wrote:
In ISCAT mode, if one double-clicks a message in the left hand RX signals pane
this presents a dialog box “Double clicking is not supported in ISCAT mode”.
When this dialog box is dismissed, the app crashes.
Many tThanks
Danny,
Why not just have JTAlert (if you use it) or WSJT-X log directly to
Log4OM? Then you wouldn't have to go through the adif import routine.
73,
Jim N6VH
On 5/20/2020 6:45 PM, DX Jami via wsjt-devel wrote:
Michelle,
My logging program is Log4OM ver2. I routinely import my WSJT-x adi
Hello all
I have noticed minor things in mainwindow.cpp source code. If they are
already known, sorry about this.
v2.2.0 rc1 mainwindow.cpp :
1. FT4 background color of mode lable depends on previous mode.
The background color difinition is missing in setup_status_bar
(bool vhf) at line
Correction here:
> I personally use DXKeeper as the central logging tool and use its "Export
> QSO's" function to "Export standard ADIF"
> back to the "wsjtx.log" file (found in the location accessible by "File/Open
> Log Directory"). DXKeeper has great tools
> for managing duplicates. When
Hi, just tried this out on some 10m Es using FT8:
I find the two stage display of decodes a little disconcerting; the
double flash of the decode button doesn't help - adds more visual
clutter? Could the user maybe have a choice to temporarily cache the
early decodes and then show them all at
On Fri, May 22, 2020 at 8:55 AM Joe wrote:
>
> Hi Kevin,
>
> On 5/22/2020 10:45 AM, Kevin McQuiggin VE7ZD/KN7Q wrote:
>
> > In ISCAT mode, if one double-clicks a message in the left hand RX signals
> > pane this presents a dialog box “Double clicking is not supported in ISCAT
> > mode”. When
What I've done is maintain two local logs: WSJT-X's native log and XLog
for everything else. fldigi will auto-ingest into XLog, and I can
easily enough create Phone and other entries manually in XLog.
I periodically use TQSL to upload WSJT-X contacts to Logbook of the
World. To make this more
Thank you Joe, glad to help, if even with a little-used mode.
As others have said, we have a small group of ISCAT users here in the west, so
we may have further info for you as time progresses.
We need to thanks James K7KQA for this as he is the driver out here for getting
people to try out
On 5/22/20 7:22 PM, Paul Bramscher wrote:
Hi Paul & all,
What I've done is maintain two local logs: WSJT-X's native log and XLog
for everything else. fldigi will auto-ingest into XLog, and I can
easily enough create Phone and other entries manually in XLog.
Please note that fldigi is able
Hi Claude,
Thanks, I'll take a look at that script. Of course I locally keep and
backup all logs that I've ever generated. If this tool automates these
kinds of merging issues, I'll certainly experiment with it.
73, KD0KZE / Paul
On 5/22/2020 1:06 PM, Claude Frantz wrote:
> On 5/22/20 7:22
Hi Michelle,
By far the best way to avoid duplicates in logs is to not set
"Settings\Reporting\ Log automatically..." . If you come back with a RR73, auto
log, and then a station comes back with a R-XX (what I term a "RR/73 Loop")
then both communication and logging can lead to duplicates in
Jim,
I can do as you suggest or I can even interface WSJT-X with Log4OM and do it
seamlessly. I chose to do it as described to Murphy-proof things as much as
possible and follow the KISS principle.
Thanks for the comment Jim. Have a great day.
Danny AH6FX/W4 -
14 matches
Mail list logo
