On 21/09/2018 7:19 AM, Black Michael via wsjt-devel wrote:
Seems non-intuitive...though I understand the idea of flagging fewer
calls. Perhaps others might comment on a preference.
Perhaps changing the color button to "Not LOTW" would clear it up for
people.
Mike
IMO, People will expect
Click on *Color Highlighting scheme* on the *View* menu.
On 9/20/2018 5:19 PM, Black Michael via wsjt-devel wrote:
Seems non-intuitive...though I understand the idea of flagging fewer
calls. Perhaps others might comment on a preference.
Perhaps changing the color button to "Not LOTW" would
All I know is that I'm all for showing who's not on LoTW. Maybe then
I'll get some peace and quiet from people in the USA when they see my
call show up in Red.
Full disclosure: I'm not on LoTW.
On 9/20/2018 16:55, Black Michael via wsjt-devel wrote:
Is this logic backwards here??? Seems we
Seems non-intuitive...though I understand the idea of flagging fewer calls.
Perhaps others might comment on a preference.
Perhaps changing the color button to "Not LOTW" would clear it up for people.
Mike
On Thursday, September 20, 2018, 4:10:27 PM CDT, Joe Taylor
wrote:
As stated
As stated in the code and in the "Quick-Start Guide to WSJT-X 2.0",
the logic currently highlights messages transmitted by stations that
have *NOT* uploaded a log to LoTW in the past year.
Of course, the test could be reversed. I did it this way because (in
the short test that I ran) it
Is this logic backwards here??? Seems we don't want the "not" here.
In displaytext.cpp
if(call2.size()>0 and !m_LoTW.contains(call2)) {
de Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
Hi Don,
On 9/19/2018 4:03 PM, Don AA5AU wrote:
Ed, W0YK, and I are thinking of changing our Ten-Meter RTTY Contest,
which normally takes place the first weekend in December, to an all-band
FT8 contest.
If you think it might be done before then, we can certainly wait. Our
thinking is that
