[Trlog] 1B67LAX Bug

[Tom Hammond]

I believe it only requires one added space... between "1B" and "67LAX"... 
e.g.  1B 67LAX, and it'll parse things correctly and you'll NOT lose the call.

73,

Tom   N0SS

At 09:24 PM 11/14/03, Jimmy Weierich wrote:
>>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
>
>
>Nope, that's the way it's worked for sometime.  TR thinks you have entered 
>a corrected callsign in the exchange field and moves it to the callsign 
>field.  A space between the fields as suggested by N6WG will prevent 
>it.  Or set CALLSIGN UPDATE ENABLE = FALSE  (and lose the update 
>feature).  A couple of years ago, I tried to get Tree to give us some way 
>(a key combination?)  to retrieve the lost callsign. He and George felt 
>that since the space in the exchange would prevent the problem no change 
>was necessary.  Search the archives for messages from me to see the 
>previous discussion, I think it was after 2000 SSB SS.
>
>Once or twice each year I still lose a call.  Software shouldn't let you 
>lose data because you did something stupid!
>
>Jimmy
>
>
>--
>Jimmy Weierich, K2LV,   ex KG2AU       <kg2au at stny.rr.com>
>Vestal, NY  USA           FN12xa
>_______________________________________________
>Trlog mailing list
>Trlog at contesting.com
>http://lists.contesting.com/mailman/listinfo/trlog