[Wsjt-devel] DXCC and Worked B4 Status documantation

[Murray Curtis]

Hi Joe

I have some documentation below for 'Show DXCC and Worked B4 Status'. I
think I sent this to the list once before but may have got lost. I'm on
Linux and I'm not confident that my Libre Office docx files will retain
all the formatting. I just did a quick test saving the existing 1.2 doc
and it came out 10% smaller. Hmm, that doesn't inspire confidence!
Could you or some other kind person please paste it into a suitable
place in the manual?

I've done a fresh check out of R3651 on Linux (Mint 14) and it compiles
and runs fine. The flatten feature works very well.

I'm in discussions with Clark AL7EK about some changes to worked B4 and
the log file it uses but we'll hold off on any code changes until after
this release.

Cheers
Murray VK3ACF

============================

Show DXCC entity and worked B4 status

This adds the name of the DXCC entity and whether you've worked this
entity and/or call before to any CQ calls displayed in the Band Activity
window. It considers JT9 and JT65 to be the same mode but does
differentiate between bands.

While it will work on the Windows version of WSJT-X it is mainly
intended Linux and Mac users. Windows users can (and should) use
VK3AMA's excellent JT-Alert utility available from http://ham-apps.com

Your worked before status is displayed as a single character with a
change of background colour:

! (bright green) New DXCC entity
~ (mid green) You've already worked this DXCC entity but not this station.
(dull green) You've previously worked the calling station.

Following the above is the DXCC entity name abbreviated if required to
fit the available space.

Requirements

WSJTX expects the file cty.dat installed in wsjtx_install. This contains
the DXCC data, is regularly updated and can be downloaded from
http://www.country-files.com/cty/

Your previous history is read from wsjtx_log.adi (found in
wsjtx_install). This file is updated every time you log a QSO from
WSJT-X (but note that it can also be erased from the file menu). You can
append or overwrite this file by exporting your QSO history as an ADIF
file from another logging program. Turning 'Show DXCC entity and worked
B4 status' off and on again will cause WSJT-X to re-read this log file.
Note that very large ADIF log files may cause WSJT-X to slow down while
searching for calls.

[Bob McCormick W1QA]

Post by Murray Curtis
I have some documentation below for 'Show DXCC and Worked B4 Status'.
I think I sent this to the list once before but may have got lost.

(snip)

Post by Murray Curtis
Show DXCC entity and worked B4 status
This adds the name of the DXCC entity and whether you've worked this
entity and/or call before to any CQ calls displayed in the Band Activity
window. It considers JT9 and JT65 to be the same mode but does
differentiate between bands.
While it will work on the Windows version of WSJT-X it is mainly intended
Linux and Mac users. Windows users can (and should) use VK3AMA's
excellent JT-Alert utility available from http://ham-apps.com

I'm using Windows v1.2.1 r3590 - really like this feature. I've been
looking for some documentation on this and must have missed the previous
posting.

IMO this would be great to get into the documentation!

Post by Murray Curtis
Your worked before status is displayed as a single character with a change

of

Post by Murray Curtis
! (bright green) New DXCC entity
~ (mid green) You've already worked this DXCC entity but not this station.
(dull green) You've previously worked the calling station.

Is it possible to change the background colours? On my system (decent
monitors / high resolution) I have a hard time telling the difference
between the mid green and the dull green. (And I had no idea what the
characters were preceding the DXCC country name until I read this post!)

Post by Murray Curtis
Requirements
Your previous history is read from wsjtx_log.adi (found in wsjtx_install).

\

Post by Murray Curtis
This file is updated every time you log a QSO from WSJT-X (but note that

it

Post by Murray Curtis
can also be erased from the file menu).

In my workflow I have been importing the ADI file into DXkeeper (log
program) and then using the erase function ... figuring that the wsjtx.log
file (which doesn't seem to get erased) was being used for the worked B4
functionality.

I think it's a lot easier to just import a whole file of the most recent
batch of "worked" stations ... rather than letting the ADIF file build up
and then having to come up with a way to determine what should be imported
(into your logging program). Maybe there's a way to accommodate this in a
future version?

Bob W1QA

[Murray Curtis]

Hi Bob

The colours for the worked before status are currently hard coded in the
source. But now that you know what the symbols mean that shouldn't
matter so much.

Your work flow with the ADI log file would not seem to be uncommon. I'm
currently thinking along the lines of giving the user a file selector in
the configuration window to choose where the worked B4 status is stored
and read from. That should help alleviate most of these problems. Note
that most logging programs (DX Keeper included I pretty sure) can easily
deal with duplicate entries. I just import the entire log and then
click delete duplicates (I'm using CQR Log).

And.. if I'm setting up an extra tab on the configuration window I have
an opportunity to add colour pickers for the marked text, and the symbol
choices too I guess. But that won't be for this release. Even the
documentation might get done!

Cheers
Murray
VK3ACF

Post by Murray Curtis
! (bright green) New DXCC entity
~ (mid green) You've already worked this DXCC entity but not this station.
(dull green) You've previously worked the calling station.
Is it possible to change the background colours? On my system (decent
monitors / high resolution) I have a hard time telling the difference
between the mid green and the dull green. (And I had no idea what the
characters were preceding the DXCC country name until I read this post!)

Post by Murray Curtis
Requirements
Your previous history is read from wsjtx_log.adi (found in wsjtx_install).

\

Post by Murray Curtis
This file is updated every time you log a QSO from WSJT-X (but note that

it

Post by Murray Curtis
can also be erased from the file menu).

In my workflow I have been importing the ADI file into DXkeeper (log
program) and then using the erase function ... figuring that the wsjtx.log
file (which doesn't seem to get erased) was being used for the worked B4
functionality.
I think it's a lot easier to just import a whole file of the most recent
batch of "worked" stations ... rather than letting the ADIF file build up
and then having to come up with a way to determine what should be imported
(into your logging program). Maybe there's a way to accommodate this in a
future version?
Bob W1QA