forked from VE3NEA/MorseRunner
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve missing/invalid exchange error reporting #341
Labels
enhancement
New feature or request
Comments
w7sst
added a commit
that referenced
this issue
Aug 24, 2024
- Add TContest.CheckEnteredCallLength virtual function - Add TContest.ValidateEnteredExchange virtual function - return ExchError via ValidateEnteredExchange - report Exchange error after hitting Enter - callsigns must contain 3 or more characters.
Below is a sample output after trying to Save a QSO containing an incomplete exchange. This example is from the upcoming ARRL Sweepstakes Contest. This error was displayed after entering an incomplete exchange and then forcing a Save QSO by pressing |
w7sst
added a commit
that referenced
this issue
Aug 25, 2024
- Add TContest.CheckEnteredCallLength virtual function - Add TContest.ValidateEnteredExchange virtual function - return ExchError via ValidateEnteredExchange - report Exchange error after hitting Enter - callsigns must contain 3 or more characters.
w7sst
added a commit
that referenced
this issue
Aug 25, 2024
Improve exchange error reporting #341 - Add TContest.CheckEnteredCallLength virtual function - Add TContest.ValidateEnteredExchange virtual function - return ExchError via ValidateEnteredExchange - report Exchange error after hitting Enter - callsigns must contain 3 or more characters. See example output in Issue #341.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
When running a simulation, entered exchange information may be incorrect when pressing the Enter key. In this case, the user may not know what is wrong with their entered exchange or what is missing. For simple exchanges, this is not a problem. However, contests using a complex exchange (e.g. ARRL Sweepstakes Contest), the missing or incorrect information is not easily recognized. This change will display a message showing the error condition.
Why
The text was updated successfully, but these errors were encountered: