Dupes are ignored and made scoring Qs upon restart

[Nate Bargmann]

Hi All.

I used Tlf for my effort in the ARRL 160m 'test this weekend.  Once
again TLF did very well.  I did notice at one point it becoming quite
sluggish with the Call field retaining the most recently worked station
for several seconds even though the Q was pushed into the log window.
I've seen this before in past events and this time it lasted perhaps
three contacts with well under 200 Qs in the log and then never happened
again.

Now to my subject issue.  During the even I worked KG4W which Tlf
recorded as the KG4 mult even though I had entered VA in the Exchange
field.  Since the mults are ARRL sections and DX entities for this
event, the presence of a section entered in the Exchange field should
have prevented evaluation of the call as a possible DXCC entity.

No matter, I exited Tlf and edited cty.dat and added KG4W into the USA
entity exception list.  Tlf dutifully rescored and I had it save a
backup.  I then noticed that my QSO score was increased by one Q as I
had one dupe in the log.  After the event this morning I compared the
main log file with the backup and the dupe Q had been changed from 0 to
2 points!

I edited the dupe back to 0 in the main log, started Tlf whereupon it
showed it was rescoring and the final score remained unchanged from the
end of the contest.  Exiting Tlf and examining the log file showed the
dupe changed back to 2 points.

That is where it stands at the moment.  The only real consequence at the
moment for me is that the claimed score is inflated by 1 Q.  However,
this could have made a mess of duping after a restart, perhaps.

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

signature.asc
Description: PGP signature