[Trlog] Exchange Window

[Michael Tope]

We had a similar problem at W6UE. Initially, Mike KA6SAR
was trying to enter the entire exchange as a long string with
no spaces. The program seemed to think it was a callsign
and copy it to the call window (e.g. 1B76NTX). After a
few tense moments, I finally convinced Mike to put spaces in
the exchange and the problem went away.  We also had a
problem with the keyboard going wild (attempting
to type a callsign or exchange would result in a long string of
gibberish characters appearing in the callsign or exchange
windows). I think this was a computer hardware problem,
however. I grabbed the $8 Fry's keyboard from the telnet
computer and swapped it in for the IBM Aptiva keyboard
and it seemed to cure the problem. Perhaps it was RF
filling the keyboard buffer or something (although it seemed
to happen even when we weren't keying). In any case, the
first 15 minutes of the contest were a bit tense :).

73 de Mike, W4EF...........................

----- Original Message -----
From: "Bob Lafont" <blafont at frontiernet.net>
To: "Jon, W4ZW" <w4zw at comcast.net>; "'TRlog'" <trlog at contesting.com>
Sent: Monday, November 03, 2003 9:24 PM
Subject: RE: [Trlog] Exchange Window


> Tree's reply:
>
> The space is something KK1L added, and isn't related to the behavior you
> are seeing.
>
> The callsign update feature is thinking your input is a callsign, and that
> is
> why it happened.  You can either turn this feature off (CALLSIGN UPDATE
> ENABLE)
> or put a space between the first half of the exchange and the second half.
>
> Tree, one additional question, what was the reasoning of adding space in
the
> exchange window?
>
> Bob
>
>
> -----Original Message-----
> From: Jon, W4ZW [mailto:w4zw at comcast.net]
> Sent: Monday, November 03, 2003 9:15 PM
> To: 'Bob Lafont'; 'TRlog'
> Subject: RE: [Trlog] Exchange Window
>
>
> Same problem here.
>
> Jon Hamlet,  W4ZW
> Casey Key Island, FL
>
> "A little bit of Paradise in the Gulf of Mexico"
>
>
>
>
> *-----Original Message-----
> *From: trlog-bounces at contesting.com
> *[mailto:trlog-bounces at contesting.com] On Behalf Of Bob Lafont
> *Sent: Monday, November 03, 2003 9:58 PM
> *To: TRlog
> *Subject: [Trlog] Exchange Window
> *
> *
> *I noticed in SSCW last weekend that after entering a callsign
> *and hitting the enter key, in either run or S&P modes, the
> *cursor went to the exchange field but one character spacing to
> *the right in the field. In other words, when moving to the
> *exchange field there was a space to the left of the cursor.
> *This was not a problem most of the time but occasionally when
> *finishing the QSO and hitting the enter key the exchange field
> *information overwrote the callsign in the call field. To avoid
> *callsign from being overwritten I would manually move the
> *cursor one position to the left in the exchange field when
> *moving from the callsign field to the exchange field.
> *Overwriting of callsigns stopped at that point.
> *
> *Was the behavior of the cursor moving one space to the right
> *in the exchange field a setup issue or a problem with the program?
> *
> *The same question applies to the exchange field overwriting
> *the callsign as well.
> *
> *Thanks
> *
> *73-Bob
> *WA2MNO
> *
> *_______________________________________________
> *Trlog mailing list
> *Trlog at contesting.com http://lists.contesting.com/mailman/listinfo/trlog
> *
>
>
>
> _______________________________________________
> Trlog mailing list
> Trlog at contesting.com
> http://lists.contesting.com/mailman/listinfo/trlog
>