[WT-support] WT 3.14: Bug with SMARTCORRECT -- still sending strange things at times

[Laurent HAAS - F6FVY]

Hi Bob et al.

Bob Wilson, N6TV a écrit :

> If you enable, SMARTCORRECT (Options, CW, Correction, Smart correction), 
> sometimes when you press [+], Win-Test sends some strange garbage before 
> it sends "TU".  It's as if the $CORRECT variable isn't cleared, or a 
> flag that indicates when $CORRECT needs to be sent isn't getting 
> cleared, in certain circumstances.

Unfortunately, it has been reported several times, but we couldn't find 
a way to reproduce it. If you find one, please inform us.

>    1. Create a new WAE log (contest doesn't really matter)
>    2. Enter SOUND in the callsign field and press [Enter]
>    3. Enter SMARTCORRECT in the callsign field and press [Enter]
>    4. Press Shift-[+].  Verify the message is set to $CORRECT ++TU--
>       $MYCALL $CR.  Close the window.
>    5. Enter F5MZM and press [Insert].  Win-Test sends "F5MZM 5NN 1"
>    6. Change the callsign to F5MZN, enter a QSO number received, and
>       press [+]
>    7. Win-Test sends "MZN TU ..."  and logs the QSO (OK, good)
>    8. Enter NOSOUND in the callsign field and press [Enter]
>    9. Enter SOUND in the callsign field and press [Enter].  Note that
>       the callsign field is empty now.
>   10. Press [+]
>   11. Bug:  Win-Test sends "SOUND TU ..."  :-)
> 
> I think the "send the correction" flag should have been cleared at this 
> point, so that this can never happen.

Actually, there is no "flag" of some sort in the code, but anyway, I 
fixed this one. The next nigthly build will include this fix.

> Similarly, when using SMARTCORRECT, sometimes you want to send a 
> complete callsign to the station just worked, instead of a partial one, 
> to make it really clear that you have his full callsign correct.  So, 
> the natural thing to do is to press [F5] and [+], but this doesn't work 
> as expected when SMARTCORRECT enabled:

(snip)

> The "send correction" flag needs to be cleared whenever $LOGGEDCALL is 
> resent, either via [F5] or [Insert], unless the call was changed after 
> $LOGGEDCALL was sent.

Easier said than done ;-)  This one needs more work, especially to 
prevent any side effects. Noted.

73

Larry - F6FVY