raenardev

    raenardev

    1 year ago
    Also question about accompanist and insets: There is an issue that
    ProvideWindowInsets
    has a certain delay, when used in fragment-based screens, which causes noticeable jumps with status bars. Are there any updates on that? (also bot closed the issue)https://github.com/google/accompanist/issues/155
    Im aware of workaround listed there, just trying to decide if it worth it to go ahead and apply that hack to all of our screens, or just wait for now 🙂
    cb

    cb

    1 year ago
    There's not much else the library can do about the delay tbh
    raenardev

    raenardev

    1 year ago
    I understand. Insets are important for proper UI building and it seems like fragments (in their current state at least) aren’t viable to use as screen unit. It was nice to move to compose while using fragment based navigation, so we still can use fragments api on screen by screen basis. Do you think that view based screens will become recommended route for Compose in future?
    n

    nitrog42

    1 year ago
    just curious, is it something that could be fixed from compose library ? the fragment library ? or the android core ?
    i

    Ian Lake

    1 year ago
    Fragments already automatically request insets on the root view of the fragment when it is attached, so insets would already be sent down to a ComposeView. The real question is: what does ComposeView do with those insets? I suspect the answer is nothing, given that inset handling isn't a part of Compose itself as of yet
    n

    nitrog42

    1 year ago
    ok so in the future, the insets should be handled by the ComposeView which should fix the issue, thanks 👍