You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Report Missing/Invalid section error/warning to the user.
Motivation
As user is entering callsign and exchange information, if the section is invalid or missing, Morse Runner will not allow the contract to be logged. The subsequent attempt should log the contact as entered.
Detailed Description
When entering exchange information, if the exchange is invalid (e.g. section), an error should be reported on the status bar (in Red). If user hits enter a second time, TU is sent and the QSO is logged as is, with the error. The error will usually be reported in the Log window. It is not necessary to open a dialog to report the error.
MorseRunner will issue a '?' to request the exchange to be repeated from the Dx Station if the Section exchange field is empty. If we start validating exchanges, then the Invalid/Missing Exchange error can be issued to the status bar. If an exchange field is missing, the cursor should stay in the current field and not move to the next field when Enter is pressed.
If we are only reporting a missing exchange, then the error should only be 'Missing Exchange'. We probably want a similar message to appear if either field is missing or invalid. I'm currently only thinking of the second field.
Additional context
N1MM reports the Missing/Invalid section when hitting enter the first time. On second attempt, a popup dialog occurs to report the missing/invalid section. User can click Yes/No to decide whether to log the QSO as is.
Tasks
The text was updated successfully, but these errors were encountered:
Summary
Report Missing/Invalid section error/warning to the user.
Motivation
As user is entering callsign and exchange information, if the section is invalid or missing, Morse Runner will not allow the contract to be logged. The subsequent attempt should log the contact as entered.
Detailed Description
When entering exchange information, if the exchange is invalid (e.g. section), an error should be reported on the status bar (in Red). If user hits enter a second time, TU is sent and the QSO is logged as is, with the error. The error will usually be reported in the Log window. It is not necessary to open a dialog to report the error.
MorseRunner will issue a '?' to request the exchange to be repeated from the Dx Station if the Section exchange field is empty. If we start validating exchanges, then the Invalid/Missing Exchange error can be issued to the status bar. If an exchange field is missing, the cursor should stay in the current field and not move to the next field when Enter is pressed.
If we are only reporting a missing exchange, then the error should only be 'Missing Exchange'. We probably want a similar message to appear if either field is missing or invalid. I'm currently only thinking of the second field.
Additional context
N1MM reports the Missing/Invalid section when hitting enter the first time. On second attempt, a popup dialog occurs to report the missing/invalid section. User can click Yes/No to decide whether to log the QSO as is.
Tasks
The text was updated successfully, but these errors were encountered: