[MobileUI] Work around some issues with the initial swipe index #302
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
Sometimes ListView doesn't react to positionViewAtIndex even after completion. Set currentIndex to the drawer works around that. To avoid seeing the initial state briefly, make it invisible at first. Additionally, show the config page for the initial setup.
Somehow it looks odd if an area gets brighter while an adjacent area gets darker. Avoid that by just not darkening the drawer.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Sometimes ListView doesn't react to positionViewAtIndex even after completion.
Set currentIndex to the drawer works around that.
To avoid seeing the initial state briefly, make it invisible at first.
Additionally, show the config page for the initial setup. This is obviously more user friendly at the beginning, but I wonder whether that makes it less obvious how to get out of the configuration dialog. It would be nice to use the back button, but that appears broken because of #301 currently.
Needs some testing on Android and Windows at least whether this improves the situation.