[guilib] DialogKeyboard: Do not register input for buttons with id >= 500 #7409
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
|
Looks valid. Not sure what the exact use-case is though. |
|
Use case is adding custom buttons to DialogKeyboard (examples: auto-completion toggles, option to switch to a T9 Keyboard instead of our default keyboard layout (which is a pain in the ass for remote users) ) |
|
OK, thanks explaining. Let's wait for @ronie. |
|
makes sense. +1 from my end. |
|
jenkins build and merge. |
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.
Allows to add custom buttons to Keyboard dialog without sending input on each button press. (atm any custom button will add its label to the input label when clickin on it)
@ronie, @mkortstiege