fix(b&w): Long ENTER not working correctly when using ADJUST GV SF #4709
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
…on 128x64 B&W radios.
pfeerick
changed the title
pfeerick
added
bug 🪲
|
There goes another OpenTX bug! 😆 And agreed, I'll add to 2.9 just in case. |
pfeerick
pushed a commit
that referenced
this pull request
Mar 10, 2024
pfeerick
pushed a commit
that referenced
this pull request
Mar 10, 2024
This was referenced Mar 10, 2024
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.
As reported on Discord.
Two different code blocks were trying to handle the long press Enter key. The resulting conflict made it very hard to figure out how to adjust the value.
This looks like it has been an issue for a long time.
If there is going to be a 2.9 update then it should be applied there as well as to 2.10 and 2.11.