[Trlog] 1B67LAX Bug

[Bob Tellefsen]

I've been through that myself.
The only fix seems to be to ensure that you put a space
between 1B and 67LAX.  Then TR will buy it move
right along.
73, Bob N6WG

-----Original Message-----
From: trlog-bounces at contesting.com
[mailto:trlog-bounces at contesting.com]On Behalf Of Mark Beckwith
Sent: Friday, November 14, 2003 4:23 PM
To: trlog at contesting.com
Subject: [Trlog] 1B67LAX Bug


Hi.  I wondered where everyone went then realized I never got turned back on
after I got back from my trip.  I figured everything that could be done to
TRlog had been done and the reflector was discontinued.

:)

I found a bug.  I searched the archives and didn't find it, but I might not
have searched thoroughly enough.  Here's something that happened to me using
6.75 in SS CW.

If I called CQ, then got an answer, then typed in the exchange with no
spaces (i.e. 1B67LAX) then tried to log it with Ctrl-Enter, the following
unacceptable behavior would take place:

The call in the callsign window would be overwritten with the spaceless
string from the exchange window, i.e. "1B67LAX".

At this point I might not remember the call I had worked, and could not get
out of the Trouble Zone without escaping backward which left me with a
finished QSO and no call or exchange to show for it.

Is this is new feature?  :)

Mark, N5OT


_______________________________________________
Trlog mailing list
Trlog at contesting.com
http://lists.contesting.com/mailman/listinfo/trlog