Add readonly and read/write radio controls #397
Merged
Conversation
This file contains 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
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 adds a new input type for setting radio frequencies as well.
Still experimenting with integrating this into Bort, and this breaks some of my existing tools (ViLA and TouchDCS) because of the unexpected change to the documentation (my fault, should have coded more defensively).
I haven't tested what happens if the aircraft doesn't support setting the frequency.
If the radio is configured to use presets, setting frequency will attempt to use a preset if one exists and if not will automatically switch it to manual mode and set the frequency.
That said, this is pretty cool. The output here is pulled from
get_frequency()