[QRG] Improve Frequency Display #784
Merged
Conversation
This file contains hidden or 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
Closed
int2001
approved these changes
Aug 22, 2024
|
Could you improve it even more to be more like in QRZ which is de facto standard.. Frequency then user input then hard coded unit. I often make mistakes when I input 28.470 not 28.470M..
|
|
@lukezaa this is the plan |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR improves the display format of frequencies in Wavelog.
Based in the used QRG unit in the
Bandsview (#544) the frequencies will be shown in the defined unit.The function
qrg_conversion()is built as generic as possible. There are various options to return different strings. If needed we could add json return aswell but maybe to a later point.Frequency Input in QSO, Contest and SimpleFLE logging will be added to a later point.