I have three `material.Button`s in a

Row

where I dynamically render buttons with different properties and have the strange ripple behaviour: the button which wasn't interacted with shows ripple effect for some reason. Notice the button in the center (video in the thread). Any ideas why this happens?

AlertDialog’s KDocs says that title’s style defaults to “h6”, and text defaults to “body1"… but the actual AlertDialogContent code defaults title to “subtitle1” and text defaults to “body2"… The Material Design guidelines suggest h6 and body1. Curious if this is a code bug or a change to the theming guidelines?

Trying to learn Compose. My goal is to have one activity and no xml/layouts. Only work with composables as views and using one loginscreen and a bottom navigationbar that reuse/saves state of its viewmodels scooped to the views. I need som help and input on how to think about this navigation setup. Code in my comment.

Is there no scroll overflow glow in compose?

I am trying to draw elliptical gradients as well as radial ones. What would be the best approach to implement something like this? The

RadialGradient

allows only one radius in the definition.

I want to create clickable sides in row with dynamic size (square, fill parent height). I try to use code (from thread), but each

Box

fills size of root, not parent size.

Navigating app using a keyboard? I am working on an app which needs to comply to WCAG 2.1 accessibility guidelines https://www.w3.org/TR/WCAG21 I tried to navigate both my own app and the Jetcaster app and nothing. Using the ARROW keys on the bluetooth keyboard I get no response from Compose apps. Is this a bug, not implemented or what is the deal? I am running beta 09 and and a Samsung Galaxy s10.

Question about the

MaterialTheme

colors and typography. If I create a

MaterialTheme

with a primary color of

Color.Blue

, and a button

TextStyle

that has the color set to

Color.White

, which color takes precedent when using a

TextButton

?

Hi guys, I'm storing Webview objects in a Singleton in order to keep their state. When my Composable gets recomposed it simply pass the webview objects to the AndroidView factory. This works perfectly when I change of Composable, however when the recomposition is triggered by an other event such as a Composable passing in front of the webview Composable, I get the following error :

java.lang.IllegalStateException: The specified child already has a parent. You must call removeView() on the child's parent first.

Any ideas ?

I have an activity with

adjustResize

mode and a

Column

with

verticalScroll

and a

TextField

inside, and when I click on the text field, keyboard obscures it, no scrolling happens. This is the latest beta. Is this a known bug/limitation? See code I use in the thread.

Inside a composable I can copy text to the clipboard by doing something like 

LocalClipboardManager.current.setText(AnnotatedString("Copied to clipboard"))

. But how can I copy to the clipboard from a callback? I want to copy the state of a

Text

when a "copy all" icon button is pressed. (The composable

SelectionContainer

is not suitable for my app for several reasons.)

What does the Animation Docs mean by "When LaunchedEffect enters composition"?

I’m seeing Kotlin’s binary compatibility tool reporting

ComposableSingletons

classes being generated and exposed as public. It seems like it might be some sort of a lambda cache, which seems fine, but does it need to be public? It’s not clear where it’s coming from, and I’m nervous about what this means for future binary compatibility because it seems to have appeared after adding a private

@Preview

function which I wouldn’t expect to have public API implications. I don’t see anything about this in the bug tracker, and I’m not sure it’s a bug anyway. Some references to this type in stack traces in this thread, but nothing specifically about whether it should be public API either.

I want to animate a corner size using TargetBasedAnimation and decide which animation value to stop at. I want to trigger the corner size animation on click, but it is automatically executed. Also, what triggers the target based animation?

Does anyone know why the typed in text here is underlined for an EditText?

This message was deleted.

I have a question regarding LazyPagingItems and LazyVerticalGrid.. is this possible? or do I have to make a custom composable for this?

navigation-compose first renders a null destination before rendering the start destination which creates a brief flicker. Any way around this?

Does anyone know how to disable passing the vertical offset event to the external lazyColumn when the focus is on the item?

I’m experiencing an issue where scrolling on a clickable composable (in this case a Card but it happens on buttons as well) makes it non-clickable the next time you try to click it, and after that it is clickable again. I guess it’s somehow related to the scroll+ripple bugfix included in beta08, but not what I want here. The card is wrapped in a Column that is not scrollable if that matters, and it’s only the banner that is written in Compose. Is there anything I can do?

Is it possible that compose automatically applies insets? When setting setDecorFitsSystemWindows on my activity, all other fragments draw behind the nav bars etc. while the compose fragment is not. When applying insets now, the other fragments look correct but the compose one has twice the padding now.

Does anyone know how to test a composable function that that doesn’t actually render UI? For instance, I have an implementation of CheckboxColors which is tied to custom theme attributes. I’d like to test that given a particular theme setup, the right values get returned.

The other thing i’m struggling with is complex semantic properties. Something like SemanticProperties.Text. The expectValue function is going to do a direct comparison. I’m looking for something more along the lines of the “argThat” type function you’d use with mockito. Would i just create a SemanticsMatcher instance rather than use expectValue I assume?

This message was deleted.

I use some composables from

androidx.compose.material

. I want to re-style/override typography theme value used by this component:

MaterialTheme.typography.caption

. Is this a correct way to do it?

MaterialTheme(
    typography = MaterialTheme.typography.copy(
        caption = MaterialTheme.typography.caption.copy(
            fontSize = 20.sp
        )
    )
) {
    // put material composable here
}

My first though was to use

CompositionLocalProvider

but

LocalTypography

has

internal

visibility modifier 🤔

Hi, I have an issue with compose, I am using ComposeView in a ViewHolder to my existing RecyclerViewAdapter which resides inside a Swipeable ViewPager. The ComposeView has a LazyRow which shows a list of cards. The issue is: When I am trying to scroll the LazyRow the ViewPager scroll intercepts which makes it difficult to scroll the items in the LazyRow. I think this is something to do with the ComposeView not able to identify the ViewTree. I have detailed the implementation on this SO question https://stackoverflow.com/questions/68038792/scroll-issues-with-lazyrow-inside-traditional-android-viewpager

I added a Kotlin file having main() to an AS Compose project for quick testing. Is there an api to execute a root composable function from a non-composable main() , similar to how we can use

runBlocking()

to launch a root coroutine from a non-suspendable main?

How would you handle a not showing a progress bar until like 300ms has gone by? I have a single state being emitted and it currently has isLoaded and my animated visibility uses that to fade between a loading spinner and the content. Would I add a third state of like isLoadedButThresholdNotMet?

What's a good way to handle loading state in compose? In my case I have multiple observables in the View Model which are wrapped by a result sealed class that contains states like success, loading and error. it doesn't feel clean to determine if the progress should show based on all the observable states I have. if( r1 is Result.Loading || r2 is Result.Loading || r3 is Result.Loading) showProgress()

Anyone ever see previews hang / never finish? Seeing this on a complicated home screen with ~15 `@Preview`s. Partly thinking I hit some edge case that’s not common. Screen is ~1500 lines of Composables + Previews in a single file. Not sure if I’ll be able to make a minimal reproducible example/app yet. (In Arctic Fox beta 03 + Compose beta 08 + Kotlin 1.5.10, but was the same in 4.2. Canary 16/Compose alpha 08, Kotlin 1.4.0)