New feature request - exclude a freqency segment (from-to) to be displayed on the band map. I find very boring to see empty band and a bunch of stations on 10 136 when I am on CW. The same applies to any FT8 frequency. Simply we need a more effective way to separate DIGI spots from CW.
73,
Martin, OK1RR
Hi Martin!
You are right, but that would make another "Tape and iron wire" fix for cqrlog.
Complete new table of reject frequency pairs would be needed. 10 pairs.... 20 paiirs....100 pairs. How many would be enough?
Editor for that table and query when updating band map.
Pity that DXCluster does not require/send mode information when sending/receiving DX spot. With that it would be very easy to implement and would not be tied to any frequency allocations.
As a quick fix, may I suggest that you set your filters at DXCluster side. There you can make frequency limitations etc. and if you do not get those spots to you DXCluster window you do not get them to band map either.
http://www.dxcluster.org/main/filtering_en.html
--
Saku
OH1KH
Hi Saku,
yes, I did. Also my "not very conventional" setting of frequency limits helps. Anyway, it is nothing serious, we can live with this. There are some more serious issues which I should track down, study if it is not OS dependent (here using Debian 9.5 sid & LXDE) and if no solution found, it should be reported.
TNX & 73!
Martin
Hi!
Perhaps we could extend Preferences/bands/frequencues table and add more modes there as it seems that most modern modes are single dialup frequencies (jt, ft modes).
On the other hand there are so many modes, and new ones are invented nearly daily (like FT8Call) that perhaps "rtty" should be renamed there as "data" and then use cw/data/ssb as limiters for bandmap.
That should be rather small fix. Actually just accept-checkboxes to bandmap settings with the corresponding comparison program part for every added callsign,
--
Saku
OH1KH