> I repeat what I said before - software should not allow one to lose
> data due to a dumb mistake.
>
I think the software designer went above and beyond in making program
recognize most of the ways an operator 'might' enter the exchange in trying
to be more efficient.
Just how far does he have to go to accommodate the variations?
The space-less exchange block you want fixed is not what is being sent (I'd
bet spaces are included through most of each exchange), nor is it what is
being reported in your log to ARRL. It's a shortcut used by the receiving
operator as provided by the software designer. Maybe, at some point, the
operator should adjust to the software and move on.
Or, heaven forbid, copy the exchange as it is sent with spaces, callsign,
etc.
> Saving what is in the callsign field before replacing it and allowing
> it to be recovered with a CTRL-key combination seems like a simple
> enough solution.
>
Because Tree (and most people) don't have that problem? I found, when I
busted a call in the callsign field, I simply typed the corrected callsign
exchange field as the exchange was being sent and it worked FB.
73,
dale, kg5u
_______________________________________________
Trlog mailing list
Trlog@contesting.com
http://lists.contesting.com/mailman/listinfo/trlog
|