Manuel Wrage

    Manuel Wrage

    2 years ago
    Why is compose using framework dialogs and popup windows instead of replicate them with composable functions?
    Luca Nicoletti

    Luca Nicoletti

    2 years ago
    It really is not
    There are
    @Composable
    functions for dialogs
    Giorgos Neokleous

    Giorgos Neokleous

    2 years ago
    There was a similar discussion recently. Dialogs will use the window manager under the hood: https://kotlinlang.slack.com/archives/CJLTWPH7S/p1572469774151700
    Manuel Wrage

    Manuel Wrage

    2 years ago
    I would like to hear the reason behind it because it could easily be reproduced with only composable functions. I already created popupmenus without native windows.
    m

    Mark Murphy

    2 years ago
    it because it could easily be reproduced with only composable functions
    I had a discussion in this channel on this topic a month or so ago. Google's argument is that your approach only works if the child "window" is limited to be shown in the boundaries of the parent window. By definition, a window cannot draw outside of its boundaries, which means that a popup drawn by a window cannot go outside of the window. While in many cases that may be acceptable, once you start thinking of freeform multiwindow (e.g., Chrome OS devices), it starts to become a bigger limitation.
    Manuel Wrage

    Manuel Wrage

    2 years ago
    Thanks for the explanation sounds reasonable. Looks like i will have to write my own dialog thing😄
    r

    romainguy

    2 years ago
    Why don't you want to use Windows for those popups?