• myanmarking

    myanmarking

    1 year ago
    is there any standard way of preserving the same viewModel instance across composables navigation, for instance, BottomNavigation?
    myanmarking
    zhuinden
    +3
    23 replies
    Copy to Clipboard
  • zhuinden

    zhuinden

    1 year ago
    [SOLVED] I updated Compose in my sample (example-dogs) to 1.0.0-beta08, now if I tap 4 dogs at the same time (thus "opening 4 pages quickly"), the app crashes with the following exception (see in thread) this crash is new and was not present in 1.0.0-beta07
    zhuinden
    Zach Klippenstein (he/him) [MOD]
    +2
    13 replies
    Copy to Clipboard
  • zhuinden

    zhuinden

    1 year ago
    exception in thread:
    zhuinden
    Zach Klippenstein (he/him) [MOD]
    5 replies
    Copy to Clipboard
  • myanmarking

    myanmarking

    1 year ago
    how to make the icon to match parent size
    myanmarking
    d
    +1
    8 replies
    Copy to Clipboard
  • Shakil Karim

    Shakil Karim

    1 year ago
    Is there any API introduced in Beta 08 for Screen Transitions Animations ?
    Shakil Karim
    Jesse Hill
    +3
    9 replies
    Copy to Clipboard
  • n

    nglauber

    1 year ago
    I’m trying to add an error message below the
    TextField
    . I’m setting
    isError
    to true ~and adding
    semantic { error("Message") }
    modifier~… do I need to do something else?
    n
    Colton Idle
    5 replies
    Copy to Clipboard
  • myanmarking

    myanmarking

    1 year ago
    does DrawScope.drawRoundRect support only partial round corners (ie, only at start-top and start-bottom) ?
    myanmarking
    1 replies
    Copy to Clipboard
  • s

    Steven Elliott

    1 year ago
    When using a text field is there a way to prevent the composable from triggering the onValueChange callback? For example let's say I only want the text field to allow numerical input.
    s
    Sean McQuillan [G]
    +1
    5 replies
    Copy to Clipboard
  • tylerwilson

    tylerwilson

    1 year ago
    I have a Compose view that scrolls with maybe 56 ‘subviews’ and performance is not good. I know the Compose team is still working on optimization, but is there anything I can do to measure performance or provide info to the team to assist? I tried using the latest layout inspector, but it just crashes the app. Thanks.
    tylerwilson
    Colton Idle
    +2
    10 replies
    Copy to Clipboard
  • s

    Slackbot

    1 year ago
    This message was deleted.
    s
    1 replies
    Copy to Clipboard