Replies: 2 comments 1 reply
-
|
Consolidating all inputs and displays to MHz works fine for this program. Even HF listening only really needs to have 5 digits right of MHz at the most, as in 3.59055. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
This is now merged into master branch. On the command line and in the configuration file frequencies must be specified in Mhz and not Hz. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Ham2mon command line options requires user input as Hz (hertz). The GUI displays in MHz (megahertz). The lockout and priority files in this fork are MHz and Hz respectively. The recently added channel log changes use MHz.
For the user interface (command line, curses interface, channel log), is there any reason these shouldn't exclusively use MHz? I find this more natural to work with but not sure if there are use cases that make better sense to have Hz.
Of course one reason not to change is that this would be user impacting. I am asking more for technical reasons but any feedback on user impact would be appreciated.
Internal processing is done in Hz and I am not asking about that use.
Beta Was this translation helpful? Give feedback.
All reactions