This is my last post and I will move on. Yes, I know about the "Imported QSO
is ignored" feature when importing and I use it all the time. But even when
you select that (it's the default), you can still have situations in which
duplicates are imported.
The point is there are all sorts of
I'm trying to understand the issue. Let's say I work you at some point on 20M
CW, then I work you again in a contest again on 20M CW. I import the ADIF file,
are you saying that you should get a warning that I've worked you before? I
don't understand why that would be a problem. Like many of
Paul,
I agree and dupes can appear in the log for many reasons. Here are a couple:
1. When an FT8 QSO does not complete the first time, you often need to send
the 73 message a second or third time and this can cause the QSO to be logged
two or three times if you are not paying attention.
Hi Dan
Re garding dupes, I do not mean during a contest (every contest program
will do that) but for the general log.
Example
I have run a specific contest program, and have exported to an adif
file. I need to import this file into DX4Win. This is where each
imported QSO should be compared to
I like all three of your suggestions. I know that I would use them frequently.
73,
Dave, N4QS
-Original Message-
From: dx4win-boun...@mailman.qth.net On Behalf
Of Paul GRANGER
Sent: Wednesday, November 27, 2019 10:49 AM
To: REFLECTOR dx4win
Subject: Re: [Dx4win] Ideas for
#1 - For a specific time period (like a contest), turn on contest mode (QSO -
Contest Mode). Make sure to check off contest mode. I think it now resets
when you exit when it used to stay on until you unchecked. It will then let
you know of dupes and give a serial number. Works nice for
Steve,
Here is my email.Mike is correct - the "ini" file is now called
config.txt. It should be in your SAVE directory.
73, John K9EL
-Original Message-
From: John K9EL
Sent: Monday, November 25, 2019 6:45 PM
To: 'steve sala' ; 'dx4win@mailman.qth.net'
Subject: RE: [Dx4win] lost
In version9 it's called config.txt, not .ini
--
73,
Mike Cizek W0VTT
-Original Message-
From: dx4win-boun...@mailman.qth.net [mailto:dx4win-boun...@mailman.qth.net]
On Behalf Of Steve K7AWB
Sent: Wednesday, November 27, 2019 12:04
To: dx4win@mailman.qth.net
Subject: Re: [Dx4win] .ini
#3 would be nice (automatic upload to Clublog)but I'm just happy with
whatever features they do. The other two items are of no interest to me,
thus I didn't comment on it..
K4TK
Tim Moore
PMP
On Wed, Nov 27, 2019 at 10:49 AM Paul GRANGER wrote:
> I did not see much
Stephen k7awb
> On Nov 26, 2019, at 7:41 PM, steve sala wrote:
>
>
> In trying to find my logbook window,
> John advised me to find my .ini file and do something with it (I cannot
> access his email from him as I write this). I went all through the
> application looking for an .ini file
I did not see much reaction to this...
Le 25/11/2019 à 10:06, F6EXV a écrit :
> Hi all
> Ideas for development :
> 1/ Be "warned" when a QSO is a dupe
> For example, when we import a contest log, we work the same stations
> over and over again. It wouod be nice to get a warning, or a message
>
Hi all
Following an update of JTDX yesterday, JTDX does not deam to reckognize
the log anymore. I deleted it (in jtdx), then I exported my FT8 QSO from
DX4Win to adif format, named that file wsjtx_log.adi and copied it onto
the JTDX file.
Of course there are many fields that JTDX nprmally does
12 matches
Mail list logo
