[TRLog] What happened?

[Udo Lautenbach DL2ZAV]

> >
> >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.
> >
-----Ursprüngliche Nachricht-----
Von: Jimmy Weierich <kg2au@stny.rr.com>
>
> 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.
> ...
>
> Again, the real problem is that what may be a valid call in the
> callsign field disappears!
>
>
The same is true for the European VHF. You need to turn off CALLSIGN UPDATE
ENABLE or every grid locator will overwrite the call sign field because
every 6 digit grid locator could also be a call sign.
Maybe this could be changed some time. In the above case, inside the program
there must be something like
FoundValidGridLocator := True    as well as
FoundValidCallsignInExchangeField := True
Now, the parser should give precedence to that what needs to be in the
exchange field over something that only is allowed to be there. In other
words, if it matches a locator, then it is a locator, not a call sign. In
very exotic cases, we can always manually update the call sign field where
only call signs are allowed for logging.

Parsing grid locators leads to another item for the wish list concerning
European VHF:

-----Ursprüngliche Nachricht-----
Von: Andy Cook, G4PIQ <g4piq@blacksheep.org>
An: <trlog@contesting.com>
Gesendet: Sonntag, 2. Mai 1999 22:32        <<<really not addressed since
then?>>>
>
> Also, a plea for an additional function is to do the distance / bearing
> calculation on a distant locator as it is typed in the exchange field in
the
> same way as it works in the callsign field. After moving from a package
> where this worked, you don't know how lost you are until can't calculate a
> bearing quickly mid QSO to confirm that you have the antennas pointing the

> right way.
>
>
Very true indeed.
I understand that unlike the content of the call sign field, the exchange is
being parsed not while being entered but only after hitting Enter. But would
it be possible that if TR finds an incomplete exchange, i.e. a locator but
no QSO number, after this Enter it at least evaluates that locator, showing
distance and bearing as if entered in the call sign field. (qsl mode =
standard)
It is of little use to know in what direction he has been AFTER he is in the
log. It's no real workaround to write the call somewhere else, delete the
call sign field, enter the locator there, turn the antenna, delete call sign
field again, re-enter call, put locator in exchange field and then go on.


--
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