forked from VE3NEA/MorseRunner
-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
314 nil when logging a partial callsign (#316)
After entering a partial callsign and exchange information, the user will hit `Enter` to finish the QSO and log the QSO. The QSO is not logged. This was caused by the logging module only comparing for a perfect match against the caller callsign and not considering the common occurrence of a partially-correct callsign. Code was changed to allow a partially-correct callsign. This allows these QSO to be included in the log as expected. Checkin notes: ``` Improve handling of partial callsign matches - Report both callsign and exchange errors in QSO log. - Add argument to IsMyCall to enable random result for lids. ``` Issue #315 will add improved messages for the partially-correct callsign case. This next review will be posted soon. Once the second pull request/review is submitted, I will post an engineering build for testing. Stay tuned...
- Loading branch information
Showing
4 changed files
with
31 additions
and
18 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters