Work without firstResponder #78
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
|
@michaeltyson Any comments on this pull request? |
|
Oh, I'm sorry @phatmann, I thought I'd already responded to this! I guess not =) |
michaeltyson
added a commit
that referenced
this pull request
Jan 17, 2014
Work without firstResponder
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.
In my app I have a view that has no text fields, but the user needs to have full access to the view even when the keyboard is showing (because another view has a firstResponder). This pull request allows for this use case. If a view managed by TPKeyboardAvoiding does not contain the first responder, the contentInset is still adjusted in order to let the user scroll to see the whole view.