Welcome to the Bug Tracking System for the Win-Test contest logger. Things to note :
- Always perform a search on both open and closed tasks before opening a new one. Your bug might already have been reported.
- Only one bug per task
Please don't ask for feature requests here but on the mailing list.
Thanks for your help. Olivier F5MZN and Laurent F6FVY
Task #126 — SMARTCORRECT: $CORRECT not cleared by [F5][+] or [Insert][Esc][+]Attached to Project— Win-Test
Win-Test isn\'t clearing $CORRECT if you press [F5][+] or [Insert][Esc][+] to resend the full and complete call sign (to override default SMARTCORRECT behavior for one QSO).
Case 2: 1. - 4. Same as above 5. Press [Insert], wait for call to finish sending, press [Esc] to halt CW at end of call, then immediately press [+] to send TU. 6. Bug: Win-Test sends F6FVY FVY TU ...
In sum, $LOGGEDCALL should be saved somewhere whenever it is done being sent. Then, just at the moment that $CORRECT will be sent, $CORRECT should be set to an empty string IF the callsign currently in the callsign field is identical to the saved value of $LOGGEDCALL. Otherwise, $CORRECT should be set to the appropriate prefix or suffix and sent.
I can confirm the same point than N6TV. When F5 is sent, [+] key should be only: \"TU ...\" without the $CORRECT code.