Hi Daniel,
if it were me making the decision, I would probably not accept such a
contribution. I say this because it is the thin end of the wedge and
even though it may be a simple concept it would surely lead to many
follow up requests about tracking the multitude of DX'ing goals that
occupy many Amateur Radio operators. The true complexity of doing this
well is illustrated by looking at the capabilities and documentation of
an application like DXKeeper in the DX Lab Suite logging program that
does this sort of thing so well. As I said above, we are not in the
business of re-inventing the Amateur Radio logging application, not
least because many users have chosen their logging application and don't
need the complexity of parallel maintenance of multiple contact
databases. We have taken the route of imbuing WSJT-X with a powerful
mechanism to allow multiple applications to access status and decode
information in near real-time, JTAlert takes advantage of this and there
is no reason why other logging applications or bridging applications
like JTAlert cannot do so too to provide the information you are looking
for.
What is currently provided by WSJT-X is only suitable for the most
casual operator, as soon as you start trying to track the vastly more
complex goals of award chasing and other DX chasing it becomes a large
distraction, of development and maintenance effort, from the prime
purpose of WSJT-X which is probably best described as an extension to
your rig that allows the use of innovative new digital modes for Amateur
Radio communications and propagation studies.
73
Bill
G4WJS.
On 07/05/2018 10:14, Daniel Ekman wrote:
If someone implements this, will it be accepted ?
This has been on my list of stuff to investigate for a long time and
it seems like a good simple feature. Not too easy to implement in code
(last time I checked) as the relevant information is not available at
the decision making point and need to be passed through several
functions to reach the deciding part. Band information is already
present in the ADIF so frequency would probably not be needed.
Checkbox to enable "Per band DXCC".
I'm not saying that the main code base should implement all JTAlert
features, but a few simple ones wouldn't hurt ?
On Mon, May 7, 2018 at 10:35 AM, Bill Somerville
<[email protected] <mailto:[email protected]>> wrote:
On 07/05/2018 04:27, Charles Otnott via wsjt-devel wrote:
Sirs,
Please allow for an entity to be shown as
NEW DXCC on a per band basis.
My particulars apply:
Program Version: 1.9.0-rc4
Operating System: MS Windows 7
Problem: Program does not allow for an
entity to be shown as "NEW DXCC"
on a per band basis.
Exact sequence of steps: Program
automatically shows an entity as
"NEW CALL" once the entity is worked
anywhere.
73 & Best DX
Charlie
WD5BJT
Hi Charlie,
WSJT-X takes a very simple view of "worked before", we are not in
the business of re-inventing the Amateur Radio computer logging
and DX tracking application, there are many excellent ones already
out there and some of the best are free software like WSJT-X
itself. As you are running on Windows you have the excellent
JTAlert companion application available (similar tools are
available for other operating systems). JTAlert has very rich
capabilities to alert you of "new ones" as they are decoded where
the definition of a "new one" is highly configurable and should
meet the objectives of most categories of DX chasers.
73
Bill
G4WJS.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
