-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/chapter drawer #485
Feature/chapter drawer #485
Conversation
Wouldn't activating it by clicking a button be better? Because swiping is reserved for changing to next/previous chapter? |
I thought the same, however the swipe gesture of the drawer superimpose over the one of the gesture recognizer and since it is limited to 60 on the left side it is easy to differentiate between the both of them. As for why I didn't use a button. I simply haven't found a place I find suitable and think it is more intuitive to swipe. |
Also adding a hard margin to WebView to allow for that swiping gesture makes the text off-center Edit: |
…rawerButton in the middle of footer
No problem. I welcome other opinions and I can't complain to you since I myself am also very nitpicky sometimes. I changed it as yous suggested and left the button as a permanent in there. The setting to enable the drawer now works as a swipeGesture enabler. I really like to be able to swipe to open the drawer, so I really want to let it in there. |
In the latest commits I added a ts file, which helps to pass props for navigation.navigate. |
Yeah, it makes sense to define it at a single place than creating the params object everywhere. |
Information
This feature adds a drawer to the ReaderScreen which allows the user to see chapters and switch between them.
Additional package
Problem