FWIT, my home-brew software (Mac) reads the ALL.TXT file every time it updates.
It also keeps my log in a separate list and a matrix of grids worked on
various bands.
If the reported station shows a grid, that grid is checked against the matrix
for grids already worked on the current band.
If the station is in a grid not already worked on the current band and it is
calling CQ it goes into one target list and if it is not calling CQ it goes
into a separate target list. This allows me to identify all stations in grids
not worked on the current band, whether they are calling CQ or whether they are
working another station.
To prevent ALL.TXT from choking my software, I truncate it periodically.
Whenever the log file updates, the program updates the log list and the grid
matrix.
Generally, I write software only for my own use (in Xojo), but if anyone is
interested I would be happy to provide more information.
BTW, I am an active user of pskreporter <http://pskreporter.info/>, and it
seems to show that my signals have satisfactory reach. I am QRV on 160, 30, 20
and 17 meters most days and 6 when it shows any sign of life. My station is
located in Vermont but I operate remotely from my winter QTH here in California.
Thanks to the development team for a terrific application…. WSJT-X RULES!
Best wishes to all.
73, Ed
W1KOK
> On Feb 8, 2018, at 8:24 AM, Daniel Ekman <kne...@gmail.com> wrote:
>
> AFAIK, it's only CQ's that are checked. If someone calls you on a band you
> have already worked on it will look the same if it was unique.
> I've thought about this question as well since 1.6.x, calling it "per band
> dupe/CQ check" or something like that in my todo list.
> At a first glance the problem is that the band data is not available to the
> checking function and it needs to be passed through several functions to
> reach it. It is possible though, as both the frequency and the band is in the
> adif log.
> I'm on linux so AlarmeJT is an option for me atleast. But I'm already using
> cqrlog to handle the logging so a quick manual check will tell me if it's a
> new band, still would be nice to handle automatically.
> Even if I come up with a working solution I'm not sure if it will be added to
> the dev branch, perhaps someone can hint on this ?
>
> On Thu, Feb 8, 2018 at 5:00 PM, Ed Stokes <w1...@comcast.net
> <mailto:w1...@comcast.net>> wrote:
> The question was whether this capability might be built into the WSJT-X
> software.
>
>
> ------------------------------------------------------------------------------
> 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
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
