[TRLog] What happened?

[Jimmy Weierich]

Ok, after playing some more with TR, I understand what's happening, 
there's a fourth scenario that should have been in my previous 
message:

4. TR recognizes an apparently valid callsign in the exchange field, 
but an incomplete exchange. It moves the apparently valid call to the 
callsign field and does not log the contact.

This can be caused by running the exchange elements together to 
create what appears to be a valid callsign, at the same time making 
the exchange incomplete. This is what happened to me and apparently 
to the person who first reported the problem. It can also occur when 
a corrected callsign is entered in the exchange field and an element 
of the exchange is omitted.

Setting CALLSIGN UPDATE ENABLE = FALSE will avoid the problem, but 
sacrificing a useful feature to avoid a problem doesn't seem like the 
best solution.

In the above scenario, if TR would leave the callsign field as is and 
not log the QSO it would avoid the problem while still allowing 
updated callsigns in the exchange field. I don't see any negative 
effects from doing this.

Again, the real problem is that what may be a valid call in the 
callsign field disappears!

Jimmy


>  > >I've been using TR for several contests. Over the weekend in the sweeps, I
>>  >noticed something peculiar. Sometimes in S & P, I would press ENTER to log
>>  >the contact and the exchange data would overwrite the callsign field. The
>>  >entry would not move up and be logged. So, I would edit the callsign field,
>>  >separate the exchange components by a space, hit ENTER... then it would
>>  >record the QSO. Was it me or TR?
>
>If you have CALLSIGN UPDATE ENABLE = TRUE (which I think is a default
>in the SS) - the program thought what you had in the exchange window
>looked like a callsign.  Either turn off CALLSIGN UPDATE ENABLE - or
>make sure you put a space in as needed.
>
>Tree
-- 
Jimmy Weierich, KG2AU       <kg2au@stny.rr.com>
Vestal, NY  USA           FN12xa

--
FAQ on WWW:               http://www.contesting.com/FAQ/trlog
Submissions:              trlog@contesting.com
Administrative requests:  trlog-REQUEST@contesting.com
Problems:                 owner-trlog@contesting.com
Feature Wishlist:	  http://web.jzap.com/n6tr/trwish.html