• t

    Thiago

    1 year ago
    Compose Text Team there is a wrong copy/paste here :
    t
    jim
    2 replies
    Copy to Clipboard
  • t

    Thiago

    1 year ago
    Is there a console logger (like Logcat) to Compose Preview? I would like to log/print some Compose behaviors without deploy to a device.
    t
    1 replies
    Copy to Clipboard
  • d

    Denis Sakhapov

    1 year ago
    Documentation is broken? All the examples there show
    //Unresolved: androidx.compose. …
    https://developer.android.com/reference/kotlin/androidx/compose/animation/package-summary#animate
    d
    e
    2 replies
    Copy to Clipboard
  • s

    Sam

    1 year ago
    Can someone from the core team share insight on the reason for the name change? Coming from SwiftUI, Stack is quite familiar nomenclature!
    s
    b
    +4
    6 replies
    Copy to Clipboard
  • Archie

    Archie

    1 year ago
    Text
    composable when not placed in a
    Surface
    seem to not apply
    Material Theme
    correctly. So when I do:
    Column {
        Text()  // This text color is black in both light and dark theme
    }
    It seems that
    ContentAmbientColor
    is not properly set for
    onBackgroundColor
    (composables not part of a surface). Its really hard to trace what exactly is the problem though, as routing to sources in the IDE is currently broken.
    Archie
    l
    2 replies
    Copy to Clipboard
  • Prashant Priyadarshi

    Prashant Priyadarshi

    1 year ago
    How to make scrollbars in a ScrollableRow always visible. I am looking for something like android:fadeScrollbars="false".
    Prashant Priyadarshi
    jim
    +1
    5 replies
    Copy to Clipboard
  • z

    zoha131

    1 year ago
    If a parent compose collect a
    Flow
    from
    ViewModel
    as
    state
    and it’s multiple children also collect the same flow as state then would it hamper the performance? I have TextFields in different layer. So passing state would make the code messy. Thats why wanted to collect the same flow from multiple Composables.
    z
    Zach Klippenstein (he/him) [MOD]
    2 replies
    Copy to Clipboard
  • Prashant Priyadarshi

    Prashant Priyadarshi

    1 year ago
    I am trying to move to compose 1.0.0-alpha04 and I have updated the new compiler dependency androidx.compose.compiler:compiler:1.0.0-alpha04 but still I am getting the below error, any idea why?
    Execution failed for task ':app:prepareDebugKotlinCompileTask'.
    > Could not resolve all files for configuration ':app:kotlin-extension'.
    > Could not find androidx.compose:compose-compiler:1.0.0-alpha04.
    Prashant Priyadarshi
    2 replies
    Copy to Clipboard
  • ppvi

    ppvi

    1 year ago
    you need to update AGP to alpha13
    ppvi
    1 replies
    Copy to Clipboard
  • d

    Daniele B

    1 year ago
    I was reading that in 1.0.0-alpha04, the
    LazyColumnFor
    issue about remembering the scrolling position was fixed. But I just checked and it’s not, at least not automatically. My use case is very simple: a list of elements; click on one element to display the detail page; going back to the list; the position is reset to the top, and not kept So, do we need to explicitly set that it should be remembered? And How? I mean that would be strange, as in the normal Android view system, the list scroll position is remebered when you go back to the list screen.
    d
    Andrey Kulikov
    +2
    17 replies
    Copy to Clipboard