> > How about changing the QSO subtotals in the program to QSO without
> > dupes. So you can tell how many real qso you have (would be better
> > if other line with dupes could be included) (I'm talking about the
> > logging screen, not the summary sheet)
> >
>
> I've been nagging Tree to do this for years. I'm glad to see I'm not
> the only one who thinks this makes more sense than the current
> method. So far Tree has resisted all my moans, but maybe if more
> people agree, and tell Tree so, he'll cry uncle on this as well.
The basic problem with this is keeping track of the dupes and
coming up with correct QSO numbers. You obviously want your
QSO number to increment if you work a dupe. The two numbers are
the same thing currently in the program. I have looked a couple of times
at making the two separate and always end up walking away from it
because it is too complicated.
I think the only way it would ever happen was if I could be made
to believe that it would have a positive impact on my contest scores.
> (OTOH, I hope he doesn't cry Uncle on the "editing the log" issue. I
> don't want to have to run a fancy whiz-bang multi-megabyte computer
> in the shack just so he can keep the log in memory -- which he has
> always said he'll have to do in order to implement this feature [or
> go to binary files, and I don't want that either].)
This is about 20 db more complicated than doing separate QSO numbers,
so I think you are safe.
Tree
--
FAQ on WWW: http://www.contesting.com/trlogfaq.html
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
|