Re: [Dx4win] Ideas for development

2019-11-27 Thread n4qs
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 ways to get duplicates into the log and you 
have no way to identify them.  I was just trying to agree with Paul that it 
would be a nice feature to have a function or utility within DX4WIN that would 
help us identify potential dupes.

73,

Dave, N4QS



-Original Message-
From: dx4win-boun...@mailman.qth.net  On Behalf 
Of David Kozinn, K2DBK
Sent: Wednesday, November 27, 2019 2:16 PM
To: 'Paul GRANGER' ; 'Dan Violette' ; 
'REFLECTOR dx4win' 
Subject: Re: [Dx4win] Ideas for development

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 us, this happens all 
the time.

If you're talking about preventing a truly duplicate QSO from being imported 
(same band, mode, and time), that's what the "Imported QSO is ignored" setting 
is for on the Options for duplicate QSOs dialog when importing. 

I use this all the time because for FT-8, I just feed it my whole log every 
time I import and it ignores the duplicate.

-Original Message-
From: dx4win-boun...@mailman.qth.net  On Behalf 
Of Paul GRANGER
Sent: Wednesday, November 27, 2019 2:13 PM
To: Dan Violette ; 'REFLECTOR dx4win' 

Subject: Re: [Dx4win] Ideas for development

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 the global log and show someting when itis a dupe (same band  and 
same mode)
73
Paul F6EXV

Le 27/11/2019 à 20:01, Dan Violette a écrit :
> #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 casual contest 
> efforts.
>
> #2 and #3 have been talked about here but I would not expect to see and have 
> not seen a possibility list of future updates.
>
> Dan KI6X
>
> -Original Message-
> From: dx4win-boun...@mailman.qth.net  
> On Behalf Of Paul GRANGER
> Sent: Wednesday, November 27, 2019 8:49 AM
> To: REFLECTOR dx4win 
> Subject: Re: [Dx4win] Ideas for development
>
> 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 
>> being copied automatically into the "Notes for this QSO" for example, 
>> that this is a dupe.
>> This dupe info should also be notified for a standard QSO, being 
>> input the normal way.
>>
>> 2/ Link the FT8 programs, so a QSO entered there is automatically 
>> transfered to DX4Win, without going through the import procedure.
>>
>> 3/ Allow automatic upload to Clublog, which MANY of us are using.
>>
>> If many users support these developments, maybe they will be taken 
>> care of...
>> Thanks
>> Paul F6EXV
> __
> DX4WIN mailing list
> Home: http://mailman.qth.net/mailman/listinfo/dx4win
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:DX4WIN@mailman.qth.net
>
> This list hosted by: http://www.qsl.net Please help support this email
> list: http://www.qsl.net/donate.html
>
> .
>

__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Re: [Dx4win] Ideas for development

2019-11-27 Thread David Kozinn, K2DBK
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 us, this happens all 
the time.

If you're talking about preventing a truly duplicate QSO from being imported 
(same band, mode, and time), that's what the "Imported QSO is ignored" setting 
is for on the Options for duplicate QSOs dialog when importing. 

I use this all the time because for FT-8, I just feed it my whole log every 
time I import and it ignores the duplicate.

-Original Message-
From: dx4win-boun...@mailman.qth.net  On Behalf 
Of Paul GRANGER
Sent: Wednesday, November 27, 2019 2:13 PM
To: Dan Violette ; 'REFLECTOR dx4win' 

Subject: Re: [Dx4win] Ideas for development

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 the global log and show someting when itis a dupe (same band  and 
same mode)
73
Paul F6EXV

Le 27/11/2019 à 20:01, Dan Violette a écrit :
> #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 casual contest 
> efforts.
>
> #2 and #3 have been talked about here but I would not expect to see and have 
> not seen a possibility list of future updates.
>
> Dan KI6X
>
> -Original Message-
> From: dx4win-boun...@mailman.qth.net  
> On Behalf Of Paul GRANGER
> Sent: Wednesday, November 27, 2019 8:49 AM
> To: REFLECTOR dx4win 
> Subject: Re: [Dx4win] Ideas for development
>
> 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 
>> being copied automatically into the "Notes for this QSO" for example, 
>> that this is a dupe.
>> This dupe info should also be notified for a standard QSO, being 
>> input the normal way.
>>
>> 2/ Link the FT8 programs, so a QSO entered there is automatically 
>> transfered to DX4Win, without going through the import procedure.
>>
>> 3/ Allow automatic upload to Clublog, which MANY of us are using.
>>
>> If many users support these developments, maybe they will be taken 
>> care of...
>> Thanks
>> Paul F6EXV
> __
> DX4WIN mailing list
> Home: http://mailman.qth.net/mailman/listinfo/dx4win
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:DX4WIN@mailman.qth.net
>
> This list hosted by: http://www.qsl.net Please help support this email 
> list: http://www.qsl.net/donate.html
>
> .
>

__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Re: [Dx4win] Ideas for development

2019-11-27 Thread n4qs
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.  Currently, I try to use 
ADIF Master to go into the wsjt-x log to find and delete the dupes.  But I 
sometimes miss a dupe and it ends up in DX4WIN and often gets uploaded to LOTW 
as well.

2.  For those of us who attempt to use other logging programs that interface 
directly with WSJT-X such as Log4om and DXLabs.  If I have already imported FT8 
QSOs using the wsjt-x log and then attempt to do so from the other logging 
program at a later date, dupes are often created due to the QSO time 
differences between wsjt-x and the other logging program.  I know that you can 
set the Time window to match QSO in secs (other logs) when importing (See 
preferences, import tab), but this can still get tricky if the other log 
program tracks both beginning and ending time for the QSO.  

It would be nice if we could run a utility in DX4WIN to identify and eliminate 
dupes.  With 170,000 QSOs in my log, it is difficult to track them down on my 
own.  You idea is a good one.

I also like suggestions #2 and #3.  Great ideas that would be used extensively 
by me if available.

73,

Dave, N4QS

 

-Original Message-
From: dx4win-boun...@mailman.qth.net  On Behalf 
Of Paul GRANGER
Sent: Wednesday, November 27, 2019 1:13 PM
To: Dan Violette ; 'REFLECTOR dx4win' 

Subject: Re: [Dx4win] Ideas for development

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 the global log and show someting when itis a dupe (same band  and 
same mode)
73
Paul F6EXV

Le 27/11/2019 à 20:01, Dan Violette a écrit :
> #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 casual contest 
> efforts.
>
> #2 and #3 have been talked about here but I would not expect to see and have 
> not seen a possibility list of future updates.
>
> Dan KI6X
>
> -Original Message-
> From: dx4win-boun...@mailman.qth.net  
> On Behalf Of Paul GRANGER
> Sent: Wednesday, November 27, 2019 8:49 AM
> To: REFLECTOR dx4win 
> Subject: Re: [Dx4win] Ideas for development
>
> 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 
>> being copied automatically into the "Notes for this QSO" for example, 
>> that this is a dupe.
>> This dupe info should also be notified for a standard QSO, being 
>> input the normal way.
>>
>> 2/ Link the FT8 programs, so a QSO entered there is automatically 
>> transfered to DX4Win, without going through the import procedure.
>>
>> 3/ Allow automatic upload to Clublog, which MANY of us are using.
>>
>> If many users support these developments, maybe they will be taken 
>> care of...
>> Thanks
>> Paul F6EXV
> __
> DX4WIN mailing list
> Home: http://mailman.qth.net/mailman/listinfo/dx4win
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:DX4WIN@mailman.qth.net
>
> This list hosted by: http://www.qsl.net Please help support this email 
> list: http://www.qsl.net/donate.html
>
> .
>

__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Re: [Dx4win] Ideas for development

2019-11-27 Thread Paul GRANGER
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 the global log and show someting when 
itis a dupe (same band  and same mode)
73
Paul F6EXV

Le 27/11/2019 à 20:01, Dan Violette a écrit :
> #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 casual contest 
> efforts.
>
> #2 and #3 have been talked about here but I would not expect to see and have 
> not seen a possibility list of future updates.
>
> Dan KI6X
>
> -Original Message-
> From: dx4win-boun...@mailman.qth.net  On 
> Behalf Of Paul GRANGER
> Sent: Wednesday, November 27, 2019 8:49 AM
> To: REFLECTOR dx4win 
> Subject: Re: [Dx4win] Ideas for development
>
> 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
>> being copied automatically into the "Notes for this QSO" for example,
>> that this is a dupe.
>> This dupe info should also be notified for a standard QSO, being input
>> the normal way.
>>
>> 2/ Link the FT8 programs, so a QSO entered there is automatically
>> transfered to DX4Win, without going through the import procedure.
>>
>> 3/ Allow automatic upload to Clublog, which MANY of us are using.
>>
>> If many users support these developments, maybe they will be taken
>> care of...
>> Thanks
>> Paul F6EXV
> __
> DX4WIN mailing list
> Home: http://mailman.qth.net/mailman/listinfo/dx4win
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:DX4WIN@mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>
> .
>

__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Re: [Dx4win] Ideas for development

2019-11-27 Thread n4qs
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 development

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 
> being copied automatically into the "Notes for this QSO" for example, 
> that this is a dupe.
> This dupe info should also be notified for a standard QSO, being input 
> the normal way.
>
> 2/ Link the FT8 programs, so a QSO entered there is automatically 
> transfered to DX4Win, without going through the import procedure.
>
> 3/ Allow automatic upload to Clublog, which MANY of us are using.
>
> If many users support these developments, maybe they will be taken 
> care of...
> Thanks
> Paul F6EXV

__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Re: [Dx4win] Ideas for development

2019-11-27 Thread Dan Violette
#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 casual contest 
efforts.

#2 and #3 have been talked about here but I would not expect to see and have 
not seen a possibility list of future updates.

Dan KI6X

-Original Message-
From: dx4win-boun...@mailman.qth.net  On Behalf 
Of Paul GRANGER
Sent: Wednesday, November 27, 2019 8:49 AM
To: REFLECTOR dx4win 
Subject: Re: [Dx4win] Ideas for development

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 
> being copied automatically into the "Notes for this QSO" for example, 
> that this is a dupe.
> This dupe info should also be notified for a standard QSO, being input 
> the normal way.
>
> 2/ Link the FT8 programs, so a QSO entered there is automatically 
> transfered to DX4Win, without going through the import procedure.
>
> 3/ Allow automatic upload to Clublog, which MANY of us are using.
>
> If many users support these developments, maybe they will be taken 
> care of...
> Thanks
> Paul F6EXV

__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Re: [Dx4win] Ideas for development

2019-11-27 Thread Tim moore
#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 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
> > being copied automatically into the "Notes for this QSO" for example,
> > that this is a dupe.
> > This dupe info should also be notified for a standard QSO, being input
> > the normal way.
> >
> > 2/ Link the FT8 programs, so a QSO entered there is automatically
> > transfered to DX4Win, without going through the import procedure.
> >
> > 3/ Allow automatic upload to Clublog, which MANY of us are using.
> >
> > If many users support these developments, maybe they will be taken
> > care of...
> > Thanks
> > Paul F6EXV
>
> __
> DX4WIN mailing list
> Home: http://mailman.qth.net/mailman/listinfo/dx4win
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:DX4WIN@mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Re: [Dx4win] Ideas for development

2019-11-27 Thread Paul GRANGER
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 
> being copied automatically into the "Notes for this QSO" for example, 
> that this is a dupe.
> This dupe info should also be notified for a standard QSO, being input 
> the normal way.
>
> 2/ Link the FT8 programs, so a QSO entered there is automatically 
> transfered to DX4Win, without going through the import procedure.
>
> 3/ Allow automatic upload to Clublog, which MANY of us are using.
>
> If many users support these developments, maybe they will be taken 
> care of...
> Thanks
> Paul F6EXV

__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Re: [Dx4win] Ideas for development

2019-11-25 Thread David Kozinn, K2DBK
I disagree with respect to Clublog. It's been around long enough and is
increasing in popularity. It has a real API interface to do
uploads/downloads, and from what I've seen it seems likely that Michael,
G7VJR, is very aware that changing the API without warning would break a lot
of things and will make sure that doesn't happen. The same argument could be
made for the existing support for LoTW and eQSL, and admittedly without any
hard data, I'd bet that Clublog is used at least as much as eQSL, if not
more. 

-Original Message-
From: dx4win-boun...@mailman.qth.net  On
Behalf Of WA7AA
Sent: Monday, November 25, 2019 9:21 AM
To: dx4win@mailman.qth.net
Subject: Re: [Dx4win] Ideas for development

On 25-Nov-19 01:06, Paul GRANGER wrote:
> This dupe info should also be notified for a standard QSO, being input 
> the normal way.
There's already an option for this and it is done by enabling the Contest
Mode. The problem is that this mode gets reset every time DX4Win is
restarted. I keep asking for an option to remember being enabled on restart
or by running a command key, but...
> 3/ Allow automatic upload to Clublog, which MANY of us are using.

Not realistic, since not only do sites like this come and go, but any change
in the site's upload procedure would require a change in the DX4Win
programming, and with the plethora of log upload sites (LOTW, eQSL, QRZ,
CLubLog, etc) this would be a logistical nightmare.

The above are personal opinions, not an official DX4Win positions, of
course.

73,

Zoran WA7AA


__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html


Re: [Dx4win] Ideas for development

2019-11-25 Thread WA7AA

On 25-Nov-19 01:06, Paul GRANGER wrote:

This dupe info should also be notified for a standard QSO, being input
the normal way.
There's already an option for this and it is done by enabling the 
Contest Mode. The problem is that this mode gets reset every time DX4Win 
is restarted. I keep asking for an option to remember being enabled on 
restart or by running a command key, but...

3/ Allow automatic upload to Clublog, which MANY of us are using.


Not realistic, since not only do sites like this come and go, but any 
change in the site's upload procedure would require a change in the 
DX4Win programming, and with the plethora of log upload sites (LOTW, 
eQSL, QRZ, CLubLog, etc) this would be a logistical nightmare.


The above are personal opinions, not an official DX4Win positions, of 
course.


73,

Zoran WA7AA


__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html


[Dx4win] Ideas for development

2019-11-25 Thread Paul GRANGER
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 
being copied automatically into the "Notes for this QSO" for example, 
that this is a dupe.
This dupe info should also be notified for a standard QSO, being input 
the normal way.

2/ Link the FT8 programs, so a QSO entered there is automatically 
transfered to DX4Win, without going through the import procedure.

3/ Allow automatic upload to Clublog, which MANY of us are using.

If many users support these developments, maybe they will be taken care 
of...
Thanks
Paul F6EXV
__
DX4WIN mailing list
Home: http://mailman.qth.net/mailman/listinfo/dx4win
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:DX4WIN@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html