Fix TouchEvents being blocked by non-visible list elements #65
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
It looks like (at least in some cases) there can be ListView elements which are outside the ScrollView, which block the interaction with the visible list elements. I could not figure out what is going wrong with these elements (how they end up in front of the UI and why they block UI interaction), but apparently, if `removeClippedSubviews` on the ListView is set to `false` is a workaround for this issue. Looking forward to feedback and improvement suggestions. *Note:* This is merely a quick&dirty workaround. It might cause some performance penalties, as all list items will be rendered from the start.
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.
It looks like (at least in some cases) there can be ListView elements which are outside the ScrollView, which block the interaction with the visible list elements.
I could not figure out what is going wrong with these elements (how they end up in front of the UI and why they block UI interaction), but apparently, if
removeClippedSubviewson the ListView is set tofalseis a workaround for this issue.Looking forward to feedback and improvement suggestions.
Note: This is merely a quick&dirty workaround. It might cause some performance penalties, as all list items will be rendered from the start.