Hi Morris,
the order of fields in an ADIF record doesn't matter. The outstanding
issue with WSJT-X v2.0.0 RC5 is that it doesn't interpret ADIF record
contents case-insensitively when it could and should. For example at
least one logging application writes the BAND ADIF field in upper case
rather than the ADIF specified lowercase, i.e. 80M instead of 80m.
WSJT-X should not treat 80M and 80m as different but currently it does.
It is an easy fix that is already coded, I just need some confirmations
from users, who are seeing issues with needed per band highlighting that
they are using ADIF exports from other logging applications in
wsjtx_log.adi .
If you are seeing this issue I can send you a patched version of WSJT-X
to test.
73
Bill
G4WJS.
On 27/11/2018 22:58, Morris Wideman via wsjt-devel wrote:
Bill if one were to import from a logging program would the order of
the fields matter if we used something like ADIF Master to par the ADI
fields down to the same as that WSJT-X saves just in a different order.
Thanks 73 Morris WA4MIT
On Tuesday, November 27, 2018, 3:50:28 PM CST, Bill Somerville
<g4...@classdesign.com> wrote:
On 27/11/2018 21:30, Al wrote:
Note below the change in color for GW4HDR after I called him the
first time..
Note also that even though I had just worked N8TCP, now colored for
new call...
Hi Al,
there is one outstanding issue in the highlighting that I am aware of,
it is related to imported ADIF log files. Have you used an export from
some logging application to replace the wsjtx_log.adi file?
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
