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
From: George J. Molnar <[email protected]>
To: WSJT software development <[email protected]>
Sent: Wednesday, September 26, 2018 8:19 AM
Subject: Re: [wsjt-devel] Decode Background Colors - Suggestions
Honestly, I think WSJT-x doing the highlighting and parsing is probably a bad
idea. If we keep it simple, with just CQs and your QSO partner, it should be a
better user experience and sturdier program. Helper apps like JT-Alert do the
external heavy lifting for those that want it, so there’s no need to duplicate
the functionality.
Think that some of the well-intentioned added functionality is going to come
back and bite us.
George J MolnarArlington, Virginia, USAKF2T - FM18lv
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
