This repository has been archived by the owner on Oct 26, 2021. It is now read-only.
Extremely dirty workaround for not responsive nav buttons #425
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.
I have observed some race condition on jumping between tabs using two methods (with swipe and navbuttons) and noticed that sometimes index of tab is incorrect. Probably it's an internal bug since it's not related to any app logic.
Of course, it's not recommendable to write it manually, but 🤷♀️