[WT-support] Version 3.15: SMARTCORRECT doesn't work right forcallsigns signing portable

[Pablo - EA4TX]

Bob,
 
I'm a CW operator and I have always this "smart correction" feature
activated. But I think that in those cases (callsigns that contais a slash)
your suggestion could cause a confusion to our remote station in one of the
cases you have reported.

Your point 5. suggestion is "IC TU"; in my opinion is should be "IC/5"; your
option is a "High smart correction" and in most cases, it's too much and
could cause a confusion.

Point 8. and 11. is OK

The actual way it works, clearly is not to be a smart correction, but will
not confuse to our remote station.

73's de Pablo - EA4TX



 
 
________________________________

De: support-bounces at win-test.com [mailto:support-bounces at win-test.com] En
nombre de Bob Wilson, N6TV
Enviado el: jueves, 16 de agosto de 2007 8:35
Para: Win-Test Reflector
Asunto: [WT-support] Version 3.15: SMARTCORRECT doesn't work right
forcallsigns signing portable


If you enter a callsign that contains a slash (/), Win-Test's "smart
correction" feature seems to get confused.  It will always send the full
callsign when you press [+], no matter how little you change.  In other
words, smart correct will send a lot more than you expect when there is a
portable designator and you correct the callsign. 

Steps to reproduce:



1.	Options, CW, Correction, Smart correction is checked (or just type
SMARTCORRECT)
	
2.	Press Shift-+ and program PLUS to be:  $CORRECT TU $CR
	
3.	Enter N2IK/5 and press Insert 
4.	Change it to N2IC/5 and press + 
5.	Bug:  WT sends the full call "N2IC/5 TU" instead of just "IC TU"
	
6.	Enter N2IC/6 and press Insert 
7.	Change it to N2IC/5 and press + 
8.	Bug:  WT sends "N2IC/5 TU" instead of just "/5 TU" 
9.	Enter W2IC/5 and press Insert 
10.	Change it to N2IC/5 and press + 
11.	Bug:  WT sends "N2IC/5 TU" instead of just "N2 TU"

Without the portable designator (/), SMARTCORRECT works perfectly, only
sending the prefix or suffix as required.  But when there's a portable, it
doesn't.  Imagine hitting [+] after finally pulling out a long and difficult
callsign like HS0/IK4MRH. :-) 

I reported this bug in a private email a few weeks ago when I was beta
testing a development version.  I thought I should post it to the reflector
so that others will be aware of it when operating.

73,
Bob, N6TV