I saw the same thing several times. If I just retyped the call in the
callsign field it would do it again. I also found that putting spaces
between the components in the exchange field would fix the problem.
It occurred so infrequently that I didn't notice any pattern in the
exchange field that was making it happen. Perhaps that's because I
started trying to remember to always put spaces between the exchange
elements. I only saw it when I forgot to put in the spaces, and then
only occasionally.
>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?
>
>Also, I would love to have the cursor start at the beginning of the exchange
>line. Was that issue ever addressed? Tks.
>
>73 de Mike, N9BOR
>FISTS NR 4594 SOC # 116
>http://www.qsl.net/n9bor
--
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
|