-
Notifications
You must be signed in to change notification settings - Fork 11
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
My exchange number is also randomly abbreviated #205
Comments
How about this as a revised proposal? |
Hi, Thank you and best regards. Mike W7SST |
Perhaps we missed the use case. In a contest, the user will want to send abbreviated numeric exchange fields. Your original concern was the random behavior. The fix turned off abbreviated fields. What we wanted to disable was the random behavior for the user's station only. I'm going to reopen this issue. I'll submit an alternate solution that will remove the random behavior for the user's station. In other words, the user's station will always send abbreviated calls. |
I agree with your opinion This fix code is always full. |
@jr8ppg Once we are satisfied, I can merge mainline into your branch and we can integrate. Or, you can give the merge a try and work through the merge issues if you want, but I'll be happy to do it. Thank you again for your contributions. Let me know what you think. BTW, I merged two Pull Requests onto mainline today. Now the IARU HF Contest is available on main. Thank you, Mike |
@w7sst |
@w7sst |
The test result was OK. CQWW CQWPX JARL ALLJA |
Description
My exchange number is also randomly abbreviated.
If the exchange type is etSerialNr, etCqZone, etItuZone, etAge, etPower, it is abbreviated by a random number.
I think my exchange number should be in a fixed format.
I am asking for your opinion please.
Steps To Reproduce
Expected behavior
Actual Behavior
Reproduces how often
Version information
Additional context
Can you help?
Please let us know if you are available to help. (replace '[ ]' with '[x]' to affirm)
The text was updated successfully, but these errors were encountered: