Skip to content
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

fixed freq_low #10

Merged
merged 1 commit into from
Nov 9, 2023
Merged

fixed freq_low #10

merged 1 commit into from
Nov 9, 2023

Conversation

john-
Copy link
Collaborator

@john- john- commented Nov 6, 2023

Before this change the gui showed wrong value for Low Tune. It always showed as Min Freq no matter what range was chosen. With this change the gui shows the correct value. I tested with:

  • range on one side of center freq
  • range on other side of center freq
  • ranges that straddled the center freq
  • ranges that were outside the bounds of the rate

I am specifying range like -e 460000000-460200000.

This is my first time working with this fork so if I am missing something (likely) please let me know.

@lordmorgul
Copy link
Owner

Range is specified correctly in your example, I had not tested that check extensively enough, correction appears right.

@lordmorgul lordmorgul merged commit e92838c into lordmorgul:master Nov 9, 2023
@john- john- mentioned this pull request Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants