[Dx4win] Minor v9 bug report
WA7AA
wa7aa at comcast.net
Wed Nov 8 19:20:20 EST 2017
Hi, Paul et al.
I just uploaded an LotW file for the first time since the new version
and first of all, thank you for fixing the
Russian-oblast-messing-up-zone problem.
A minor bug is in the way that Import discrepancies are being reported.
In the past, when there was a discrepancy between the QSO data as
determined by DX4Win (or operator) and the data being reported by LotW,
the Import note in the Notes For This QSO would state the LotW value.
This is still the case for everything except for the zone value.
For example, before v9, the import note would read something like this
for, let's say HA1ABC: Import: {Zone 28}
Obviously this would be incorrect due to the erroneous zone selection
upload by HA1ABC, which is the case with well over 90% of the LotW
discrepancies.
In v9, however, this import tag reads: Import {zone 15}, which although
correct, doesn't match the LotW reported value. The other discrepancies,
i.e. IOTA, State, Grid are reporting the LotW entry. Again, this doesn't
impact the integrity of the QSO zone entries, it is simply a misleading
visual tag.
I hope I am making sense.
Thanks again & 73,
Zoran WA7AA
More information about the DX4WIN
mailing list