[Top] [All Lists]


Subject: [TRLog] WAE
From: (
Date: Sun, 6 Dec 1998 06:57:13 -0800 (PST)

Well, some progress has been made with WAE stuff.  This will be in the
upcoming 6.36 release.

1)   TR will send DUPLICATE QTC's if there are zero point QSO's in the log
(e.g. dupes) and the program is exited and restarted.  It appears to read
the qtclist.dat file to determine how many QTC's it has sent and to whom.
Unfortunately, it uses the total as the current location for sending QTC's
in the log. 

Suggestion:  Also check the last entry in QTC.dat, find that QSO, and
reset the QTC pointer.

> This was a weak part of the code.  I now look to see what the last
> QTC sent was in the QTC.DAT file and match that up to the log.  Then,
> as I load potential QTCs in, I ignore zero point QSOs.  Before, the
> program would could zero point QSOs during the first phase of that.

2)     TR will act squirrely after the "Please send some QTC's,
QTC memory is getting full" warning.  It eventually satarted sending
garbage for QTC's, despite my best efforts to send some. :-)

> Not sure what is happening here - will keep looking.  Obviously, 
> try to avoid having more than 500 pending QTCs.

Enhancement Requests:
1)  It is FAR too easy to blow away a QTC.  Using TR, we just hit <CR>
to do everything.  Then the program asks "Did *** QSL QTC ***/**?
(Y/N):" orsomething similar.  Quess what <CR> does?  It blows
away the entire QTC!  This needs to insist on Y/N.  Yes, I had to
turn off the radio and re-sent that QTC to nobody!

> It looks like I have already worked on this.  I couldn't find any
> places were this could happen.  I did find one place where pressing
> RETURN would act as a Y to finish the QTC, so I made it require a Y now.

2)  We need to be able to review the QTC just sent, and get the
number (like 172/10) after sending a QTC.  Exiting the program to
check QTC.dat causes WAY too much trouble since the QTC's get out
of sync.  (Seethe bugs above).

> When finishing a QTC, there will now be a note added to the log with
> this information.

> Tree

FAQ on WWW:     
Administrative requests:
Feature Wishlist:

<Prev in Thread] Current Thread [Next in Thread>
  • [TRLog] WAE, <=