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

Intuitive use of rigctld/rotctld #43

Closed
bjorgan opened this issue Mar 3, 2017 · 1 comment
Closed

Intuitive use of rigctld/rotctld #43

bjorgan opened this issue Mar 3, 2017 · 1 comment

Comments

@bjorgan
Copy link
Member

bjorgan commented Mar 3, 2017

Currently have to specify e.g. --rotctld-host=[HOST] in order to enable connection to rotctld (and rigctld).

Additional possibilities (in addition to current CLI options):

  • Detect availability of rotctld/rigctld automatically (and add possibility for disabling entirely)
  • Add configuration files
  • In-program configuration

Do an assessment on whether any of the above makes this more inconvenient and cumbersome or not.

rigctld autodetection will be problematic, won't know what to choose for uplink and downlink, but might be good to rethink this a bit.

@bjorgan
Copy link
Member Author

bjorgan commented Jul 24, 2017

Fixed in f0bac33 by revising the CLI flags and adding a settings screen.

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

No branches or pull requests

1 participant