extending functionality to handle footer also #17
Conversation
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
|
+1 |
3 similar comments
|
+1 |
|
+1 |
|
+1 |
return the tableview height based on sizes of data.
return the tableview height based on sizes of data.
|
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 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.
This change makes possible to place your brilliant refresh view in footer also.
It modifies a little your base class (EGORefreshTableHeaderView) to be able to setup some values using instance method. This way it is possible for my new derived class to setup different values and make it possible to place it just after table view.
I included usage example in your demo project.
Thanks for a great idea of handling table view refresh.