Thread
#compose
    Adam Powell

    Adam Powell

    2 years ago
    Ian Warwick

    Ian Warwick

    2 years ago
    nice one so I won't worry about that myself then 😄 will it be good for undo/redo scenarios as well as back stack poppin' and all that? 🙂
    actually of course it would be, looking forward to that nice 👍
    Adam Powell

    Adam Powell

    2 years ago
    undo/redo is likely to be more about the data backing your composition rather than the composition itself, curious what you have in mind there
    back stack too, for similar reasons
    though integrations with the arch components navigation library are inevitable there 🙂
    Ian Warwick

    Ian Warwick

    2 years ago
    Actually yes undo/redo is more of a data thing but the concept of going from one screen to another and back again is something we are used to with activities and the back stack, just wondering how that would be in compose and was thinking one way to achieve "going back" is to save a composition before replacing it with a new one.
    Adam Powell

    Adam Powell

    2 years ago
    sort of, but that mental model carries some other baggage. A composition without the data that created it isn't really a, "live" UI anymore
    and a composition is always a function of the data that created it
    Ian Warwick

    Ian Warwick

    2 years ago
    ok though what about data created inside a composition via
    remember
    ?
    Adam Powell

    Adam Powell

    2 years ago
    the scope of that data is dependent on where it is in the composition. If you
    remember
    something above the point where you do your nagivation, it will persist.
    Ian Warwick

    Ian Warwick

    2 years ago
    aha nice yeh 🙂
    ah ok above
    Zsolt

    Zsolt

    2 years ago
    @Ian Warwick if you need back stack functionality, compose-router already has that along with scoped savedinstancestate
    Ian Warwick

    Ian Warwick

    2 years ago
    yeh nice I saw that @Zsolt its quite cool cheers