Repository navigation
Conversation
Author
|
Hi, first-time contributor here. The DotNet Build workflow on this PR is still showing as pending rather than running - it looks like it is waiting for approval to run on a fork PR from a first-time contributor. Could a maintainer approve the workflow when convenient? Happy to adjust anything about the change in the meantime. |
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
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.
Battery 3..9 voltage entries all carried
[DisplayText("Bat Voltage (V)")], so the Quick/status views could not tell them apart. Each is nowBat3 Voltage (V)...Bat9 Voltage (V).Also in this PR, as separate commits:
Testing: built MissionPlanner.sln (Release, net472, VS2022); opened the Quick view and confirmed the battery entries are distinguishable; checked the FlightPlanner map selector.