Conversation
4f3babe to
883a169
Compare
44a2442 to
2ae1ea5
Compare
| index === self.length - 1 | ||
| ? 1 | ||
| : Platform.OS === 'android' | ||
| ? cond(eq(next, 1), 0, 1) |
There was a problem hiding this comment.
I think we may get rid of screens support for iOS now. @kmagiera promised me to fix lines breaking this implementation.
There was a problem hiding this comment.
Right, I suggest to turn off screens on iOS for the time being. Even when fixed there are still going to be some people on the old version (via expo for example). I am also confident that the fix may not be necessary, we already use screens and panning works fine with gesture handler in the non-reanimated implementation AFAIK
There was a problem hiding this comment.
Even when fixed there are still going to be some people on the old version (via expo for example)
I think this is not a problem coz it's enabled explicitly by the user by calling useScreens
There was a problem hiding this comment.
@brentvatne wdyt? should I remove screens usage?
There was a problem hiding this comment.
if it isn't then we can just disable screens on iOS temporarily :)
There was a problem hiding this comment.
What is the issue? If @kmagiera doesn't have time maybe someone else can fix it?
There was a problem hiding this comment.
I wonder how it was possible that the prev version of stack was working
There was a problem hiding this comment.
I'm not sure. @brentvatne did last one and you did this one XD
Though I only had this problem on Android when implementing it here react-navigation/reanimated-stacks#3
Otherwise the header background below shows up when header mode is none
|
in uikit example:
|
|
@brentvatne is it alpha or latest commit? |
Previously, the header height wasn't stored per screen. This resulted in header height always referring to the one in last mounted screen. As a result, the top margin for screens were incorrect. This resulted in bugs such as when you go to a screen with no header, header height will stay 0 even after navigating back. This commit stores the height for each screen separately, handling this properly.
|
Hey @satya164, create work in the I use already the branch and the alpha versions of the react-navigation-stack. Why did you disable screens (f04b9bf) in the latest alpha for modal dialogs? Using screens and also the new iOS 13 effect was one reason for me to use already the alpha. (edit: After updating from alpha.2 to alpha.5 is lost the new iOS 13 modal effect. I switched back to the old version for now.) |
Because for modals such as The only things
Please read the release notes: https://github.com/react-navigation/stack/releases/tag/v2.0.0-alpha.3 |
|
Merging this to master and continue development from there. This will make sure any new PRs and issues we receive are against the latest changes. |
|
Thanks for the fast feedback @satya164 With moving the TransitionPreset attributes into the |
This is a re-implementation of stack navigator using kmagiera/react-native-reanimated.
TODO
headerStylescreenPropschange