Murray VK3ACF wrote: > 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)
> 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! > 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. 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!) > Requirements > > 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). 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 _______________________________________________ Wsjt-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/wsjt-devel
