I agree with you Don on a way to just turn off color coding, or just let
the user decide what they want, but trying to accommodate everyone is
turning into the predicted black hole.
As far as JT-Alert, Laurie is only one person, and while he's been
trying to get the code moved to a cross-compile platform, its a slow
process.
Neil
On 9/26/2018 9:59 AM, Mark James wrote:
On Wed, Sep 26, 2018 at 9:51 AM Don AA5AU <aa...@bellsouth.net
<mailto:aa...@bellsouth.net>> wrote:
I agree with George as I've been thinking this all along since
2.0.0 rc1 came out. I don't pay much attention to the colors in
WSJT-X other than the dark purple for new DXCC. The old system of
colors worked fine for me.
I rely on JTAlert to alert me to my needs because I run two radios
and multiple instances of WSJT-X.
When running two radios and multiple instances of WSJT-X,
wsjt_log.adi is not always updated for all instances since they
are not sync'd automatically. So the color codes are not always
correct.
To update all the instances of wsjt_log.adi, occasionally I filter
my DXKeeper log to show all FT8 contacts, then export that and
name it wsjt_log.adi. I then replace the existing wsjt_log.adi
files for all instances of WSJT-X. That works great but I don't do
it that often.
To update JTAlert, I just do a "Scan Log & Rebuild" before each
operating session and JTAlert is up-to-date.
Don AA5AU
---
This email has been checked for viruses by AVG.
https://www.avg.com
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
