Re: [Tlf-devel] TLF-1.1.0 release announcement

[Andy Summers]

Hi,

I operated in a UK domestic CW contest at the weekend and I have a 
couple of usage issues I want to report whilst still fresh in my mind.

On a couple of occasions I was in the exchange field having just copied 
the received exchange. I accidentally hit F2 (sent exchange) instead of 
F1 (CQ) at that point. In panic, I hit <esc> to terminate sending CW, 
but it keeps going. I hit <esc> again and it stops. I look back at the 
display and find that I've now lost the exchange I just copied! I call 
that station again, but he's already QSY'd. I can't remember the 
exchange and I've now got a busted QSO!

I realise that TLF is trying to emulate TRLog in the way that it uses 
<esc> to progressively back up, and I know some will say that if I was 
using ESM properly I wouldn't have got into that panic, but this 
behaviour is nevertheless irritating. I think possibly a major factor in 
this is that the CW doesn't immediately terminate. I haven't checked, 
but I think there is a similar issue on SSB. This is a bit of a 'note to 
self' because I'm happy to try taking a look whether this could be 
fixed, but it's not high on my priority list.

When you're in the exchange field there's no editor function like there 
is in the call field. If I didn't get the first digit in a 3 digit 
serial I don't want to have to delete the two digits I did copy to get 
to the first digit position. TLF can also be used in non-serial 
contests, and proper editing functions are really necessary in this 
instance.

When you're editing a call (you've arrowed left and changed something) 
and you then hit <tab>, the partials window background goes black. Only 
a cosmetic issue, but it doesn't look good.

Didn't the score window previously give the number of QSO's and dupes? I 
know I worked some dupes but they don't appear.

73 Andy, G4KNO.