Code Monkey home page Code Monkey logo

Comments (5)

chrfalch avatar chrfalch commented on May 29, 2024 1

You're probably using the library a bit "upside down" - it is built for building transitions between screens - not between nested navigators. You will not see any results the way you use it - a FluidNavigator does not know how to transition between sub navigators. Use FluidNavigator for the screens and build transitions in these screens - that should probably work.

from fluidtransitions.

chrfalch avatar chrfalch commented on May 29, 2024

The Example has a nested setup with a StackNavigator. If you’re unable to integrate with other navigators please provide a snack as an example. Also verify that it works with a regular StackNavigator before creating the issue. Thanks!

from fluidtransitions.

ducpt2 avatar ducpt2 commented on May 29, 2024

this is last of my effort to trying contributed to this lib.
https://snack.expo.io/ByfA7bqjG
I'm not work with snack before, so i just push my code on snack (it simple like your example). This code work simple with react-navigation, but when using FluidNavigator it not work like i expect.
(Or i do something wrong, can you point it out???)
Can you try test with your own when you close? Do you want to make this library better? I still wonder about this.

from fluidtransitions.

ducpt2 avatar ducpt2 commented on May 29, 2024

" it is built for building transitions between screens" - That is one of my thought. Very thanks your suggestion. I will try to find out how to do this way. <3

from fluidtransitions.

plus- avatar plus- commented on May 29, 2024

You're probably using the library a bit "upside down" - it is built for building transitions between screens - not between nested navigators. You will not see any results the way you use it - a FluidNavigator does not know how to transition between sub navigators. Use FluidNavigator for the screens and build transitions in these screens - that should probably work.

What would be the solution to transition between a screen and a modal (as defined in https://reactnavigation.org/docs/en/modal.html)

for example between the ModalScreen and the DetailsScreen in this picture:
https://reactnavigation.org/docs/assets/modal/tree.png

modal must be defined at the top most stack, but I don't want to create a fluid navigator on the top most stack as I only define transition between the modal and some of the screen.

This is related to #178

from fluidtransitions.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.