Hi Uwe,
I think there is some misunderstanding of how the colour highligting is
applied. For each highlighting type the foreground and background colour
may either be specified or not. If a colour option is not specified then
no highlighting for that highlighting type and, most importantly,
another lower priority highlighting type may be applied.
This gives extra flexibility since the foreground and background colours
are applied separately. Careful choice of foreground, background and
priority can lead to one or two indications for a CQ call from a station
that your WSJT-X ADIF shows has not been worked. So for example your
example (2) below should be indicating that LZ2TU is both a new call on
20m and a new grid. Looking from the implementation side, the grid KN13
has been checked before the call LZ2TU, due to their relative
priorities, and found to be new on 20m so the background colour of pale
orange is applied. Since the foreground colour for a new grid on band is
not specified, the subsequent check for a new call on band that finds
LZ2TU is a new call on 20m causes the unassigned foreground colour to be
assigned blue. No other highlighting is applied as both foreground and
background have now been allocated by higher priority checks.
If there is a defect then your ADIF log will not contain any records of
QSOs with KN13 on 20m nor LZ2TU on 20m. If you have such records in your
log then please reply with them so I can assess why they might not have
been considered.
73
Bill
G4WJS.
On 28/11/2018 10:42, DG2YCB, Uwe wrote:
Bill, Paul, and all,
One additional observation: Seems that indeed only the foreground
color is affected by the bug. Modified my color scheme settings that
way, that all the “…on Band” colors not only have a blue foreground,
but also a somewhat lighter background. See the result in the
following screenshot:
(1) LZ2TU was correctly recognized as “New Grid”, and SV1CIF was
correctly recognized as “New Call on Band” (I worked him already on 12m).
(2) However, on both cases the foreground color switched to blue. And
there is the error. A combination of the darker background color for
“New Grid” with a blue foreground color like for “New Grid on Band”
should not appear at all.
(3) Thus, seems to be that only the foreground color is affected by
the bug. (Can be that in the code only one small command is wrong
regarding the foreground colors.)
Hope this observation helps.
73 de Uwe, DG2YCB
*Von:*DG2YCB, Uwe [mailto:dg2...@gmx.de]
*Gesendet:* Mittwoch, 28. November 2018 09:36
*An:* 'Bill Somerville'; wsjt-devel@lists.sourceforge.net
*Betreff:* Re: [wsjt-devel] Color scheme: "on band" always highest
priority?
Bill,
Yes, my wsjtx_log.adi file contains entries generated by an external
ADIF program, but band information is also in lower case. Since in
contrast to v1.9.1, WSJT-X v2.0.0-rc1 misinterpreted ADIF records with
6-digit entries for grids, as a workaround a couple of months ago I
generated one ADIF file containing my QSO history, but only using
4-digit grids. Since then, the various WSJT-X versions have been using
this file and added all their new entries to it. (Btw.: We’ve had an
email conversation on the “6-digit grid square bug” September 25^th
and 26^th , 2018. I don’t know if it has been fixed meanwhile.)
Here is one example of an entry imported from my external ADIF file:
<qso_date:8>20171126 <time_on:6>153300 <call:6>PU2YJO <band:3>15m
<freq:6>21.074 <mode:3>FT8 <gridsquare:4>GG66 <country:6>Brazil
<name:16>Oscar Julio Burd <notes:9>Sao Paulo <rst_sent:3>-18
<rst_rcvd:3>-12 <time_off:6>153700 <eor>
For comparison here an entry made by WSJT-X v2.0.0-rc5:
<call:5>VA3ZV <gridsquare:4>EN82 <mode:3>FT8 <rst_sent:3>-19
<rst_rcvd:3>-22 <qso_date:8>20181127 <time_on:6>142545
<qso_date_off:8>20181127 <time_off:6>142715 <band:3>20m
<freq:9>14.076956 <station_callsign:6>DG2YCB <my_gridsquare:6>JO42gb <eor>
73 de DG2YCB,
Uwe
____________________________________
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg2...@gmx.de <mailto:dg2...@gmx.de>
Info: www.qrz.com/db/DG2YCB <http://www.qrz.com/db/DG2YCB>
*Von:*Bill Somerville [mailto:g4...@classdesign.com]
*Gesendet:* Dienstag, 27. November 2018 22:52
*An:* DG2YCB, Uwe; wsjt-devel@lists.sourceforge.net
*Betreff:* Re: Color scheme: "on band" always highest priority?
On 27/11/2018 17:00, DG2YCB, Uwe wrote:
Many thanks for great work on the color scheme! Basic functions
work well now with v2.0.0-rc5 here at my PC. (Windows 10 64 bit)
However, there seems to be some minor bugs left. May the following
observations help you to identify them as well:
(1) Seems to be, that “New Call on Band” has always a higher
priority than “New Call”. When both are enabled, a new callsign is
always highlighted as “New Call on Band”, even when I’ve not yet
worked that station before on any band. Tried to chance priority
settings, but no effect (see screenshot 1).
(2) Same seems to be true for “New Grid on band” versus “New
Grid”. When enabled, all new grids are highlighted as “New Grid on
Band” I don’t know if it is also the case for “New DXCC”, “New CQ
Zone” and “New ITU Zone” and so on, but there was no station on
the band to check.
(3) When “on Band” settings are disabled color scheme works well.
Only one exception: I really don’t know why, but even when “New
Call on Band” is disabled, one callsign (OE3FVU) was highlighted
as “New Call on Band” (see screenshot 2). Closed WSJT-X and
started it again, but no change. What may be the reason?
Just for explanation: I’ve already changed default to my favorite
colors. “New Call” and “New Call on Band” has the same background
color, but “…on Band” with blue foreground color.
Hi Uwe,
are you using ADIF records imported from another application in your
wsjtx_log.adi file?
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
