[Dx4win] Dupes

2014-01-09 Thread PY2YP
A tool for removing dupes QSO should be great, say, the dupes QSO should be saved in a temporary file allowing the user to examine the removed QSOs before deleting the temp file. -- 73 DX de PY2YP - Cesar __ DX4WIN mailing list Home:

[Dx4win] DX4WIN Wish List

2014-01-09 Thread GW4BLE
DX4WIN Wish List PSK63 support (not a great PSK user, but PSK31 is just too slow). Thank you Paul 73 Steve GW4BLE __ DX4WIN mailing list Home: http://mailman.qth.net/mailman/listinfo/dx4win Help: http://mailman.qth.net/mmfaq.htm

Re: [Dx4win] Dupes

2014-01-09 Thread Radivoj Kar, F6GNZ
Cesare, I think it won't be good to automatically remove dupes from the log! Better have them marked by a red colour and let user decide afterwards.. 73, Radi F6GNZ Le Jeudi 9 janvier 2014 10h58, PY2YP py...@py2yp.com a écrit : A tool for removing dupes QSO should be great, say, the dupes

Re: [Dx4win] Dupes

2014-01-09 Thread Teijo Murtovaara
9.1.2014 13:47, Radivoj Kar, F6GNZ kirjoitti: Cesare, I think it won't be good to automatically remove dupes from the log! Better have them marked by a red colour and let user decide afterwards.. 73, Radi F6GNZ Le Jeudi 9 janvier 2014 10h58, PY2YPpy...@py2yp.com a écrit : A tool for

Re: [Dx4win] Dupes

2014-01-09 Thread PY2YP
You are right Teijo, a dupe definition is mandatory before thinking about removing. A dupe is a nearly exact time, say a 5 minutes window or precisely the same time, resulting either from typing old logs or importing old logs. I have faced this problem several times when working with PY0S old

Re: [Dx4win] Dupes

2014-01-09 Thread David Kozinn, K2DBK
I would like to humbly suggest that since logs can be exported, modified, and re-imported, that perhaps something like this would be better for a third-party tool. Just the discussion of defining what a dupe is shows to me that implementing such a feature as part of the core functionality of

[Dx4win] On-Going Annual country totals

2014-01-09 Thread GW4BLE
Anyone able to advise on this. In the calendar year 2014, I would like to start from scratch and keep a running total of DXCC entities worked but I want to do so from WITHIN MY EXISTING DX4WIN log, NOT by running a separate log. When connected to the cluster I want to be alerted to new

Re: [Dx4win] On-Going Annual country totals

2014-01-09 Thread Jim Reisert AD1C
Set up a group selection BY DATE, starting 2014. Then your log will only show 2014 QSOs. On Thu, Jan 9, 2014 at 4:55 PM, GW4BLE steve.gw4...@btconnect.com wrote: Anyone able to advise on this. In the calendar year 2014, I would like to start from scratch and keep a running total of

Re: [Dx4win] On-Going Annual country totals

2014-01-09 Thread Bud Semon N7CW
To add to Jim's answer, see Filter|Selection in the Help file. It is pretty complete. 73, Bud N7CW On Thu, Jan 9, 2014 at 4:58 PM, Jim Reisert AD1C jjreis...@alum.mit.eduwrote: Set up a group selection BY DATE, starting 2014. Then your log will only show 2014 QSOs. On Thu, Jan 9, 2014

Re: [Dx4win] On-Going Annual country totals

2014-01-09 Thread GW4BLE
Thanks Bud, and Jim. I just wonder if by doing that will I still be able to see previous QSOs listed in the 'other QSOs' window and will the 'reports' menu just show 2014 totals?..guess there's only one way to know... Steve GW4BLE -Original Message- From:

Re: [Dx4win] On-Going Annual country totals

2014-01-09 Thread Bud Semon N7CW
Steve, Every time you start DX4Win, you have to go to Filter, Selection and choose 2014. The QSOs in the original Selection do show up in the Other QSOs window. The Reports only cover the Selection you have chosen. My suggestion is to make the original Selection include ALL QSOs (including

Re: [Dx4win] On-Going Annual country totals

2014-01-09 Thread GW4BLE
Thanks Bud. Just been experimenting and it seems to do just what I need, great job! I've been a long-time user of DX4WIN (well over 200,000 Qs in the log) but being more of a contester I guess not realised its full potential. 73 Steve GW4BLE -Original Message- From: