Conversation
hecrj
force-pushed
the
TextInput-Maybe
branch
from
26a1a9a to
09174d5
Compare
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
2 participants
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.
Just a small addition for the
TextInputwidget.The
TextInputhas currently no*_maybemethods likeButtonhas theon_press_maybe. This PR adds them.Added Methods:
on_input_maybeon_submit_maybeon_paste_maybeThese methods, especially the
on_input_maybe, are usefull in the same manner asButton::on_press_maybeand can simplify the building of uis containing the TextInput.