Christian Falch
Christian Falch
It looks like it takes approx 0.5 secs? Same as I experienced running the Snack.
If I change FluidNavigator to StackNavigator I see that the speed is much better. I'll take a look and see, always happy to try to optimize the library!
(See last comment)
In the example it looks like this is solved for the latest releases, could you check and see? @roytan883, @jskidd3, @Jonovono
Hi, @rohan-jansen! Thanks for submitting an issue. Your example is a complex one, would it be possible to reproduce this in a smaller example on snack.expo.io?
Unfortunately It's unclear to me what the problem is just from watching the GIF...
Thanks, @hubciorz - but this seems to be working in the demo on my computer?
Could this be a problem in react-native-screens?
Hi @ntomallen! Thanks for your feature request, this is something I've been thinking of for a while already. The reason for not supporting this yet is that the library is...
The StackRouter has the history of pushed routes, but knows nothing of what the next route would be. The integration between FluidTransitions and React Navigation makes it a little bit...