After upgrading to

lifecycle-viewmodel:2.5.0-alpha01

I’m getting compile errors on classes that inherit from `ViewModelProvider.Factory`:

Inheritance from an interface with ‘@JvmDefault’ members is only allowed with -Xjvm-default option

I’ve tried fiddling all

-Xjvm-default=xxxxx

options but the error does not go away. Anyone had the same trouble?

This message was deleted.

Hi all 👋 I'm trying to adjust the style of my buttons. I'd like all my `Button`s to have the same style, same is for `OutlinedButton`s. I was able to tweak some parts like shape & surface given the

MaterialTheme

open properties but if I want to customize more, I'm stuck. For instance, I'd like to tweak the width of the `OutlinedButton`'s border and potentially its color. The only thing I can think of so far is to redefine my own

MyAppButton

tweaking what's needed (by calling built-in button composable or not, impl detail here). Can't we have ways to override

ButtonDefaults

? (using opened

var

instead of

val

or

LocalButtonDefaults

or something like that). I have the feeling that redefining custom buttons make composable less reusable and tightly coupled to custom composable rather than provided theming.

Any ideas how I can align the text centered? I tried everything I'm aware of but the text doesn't move vertically except padding.

I’m running 1.1.0-rc02 compiler with 1.1.0-rc01 dependencies (both tooling and tooling-preview). Using AS bumblebee and compose previews aren’t rendering. Does anyone know if this is a known issue. Couldn’t find anything relevant on issue tracker

I hope this is the place for Coil questions. How do I point to my own instance of OkHttp with Coil and rememberImagePainter?

I have designed a custom switch in Jetpack compose and not able to use it properly it is not respecting its parent and getting out of the view.

Hii, I wanted to know if it is better to keep State<UiModels> in view models or keeping StateFlow<UiModels> in view models and then in compose layout collect their value to a state? What would be preferable here?

Hello, I was wondering if people encounter the same issue while using https://github.com/google/accompanist/tree/main/navigation-material with ModalBottomSheet with Compose? If i swipe down the modal the lifecycle of the NavBackStackEntry goes to the

ON_DESTROY

state however if I’m doing the classic back the lifecycle stop at

ON_STOP

and never reach the

ON_DESTROY

Is there a way to know whether

LazyListState.isScrollInProgress

was triggered by user or not? Documentation says "Whether this ScrollableState is currently scrolling by gesture, fling or programmatically". I think I can use

InteractionSource

to catch drags, but it would not cover flinging and maybe some other user-initiated scrolls.

I have a CoordinatorLayout which contains (FragmentContainer + BottomNavigation)

For setting clickable links within text, we need to use AnnotatedString with ClickableText. However, I've noticed that the ClickableText consumes the pointer events even if the tap doesn't correspond to a clickable region of text, and thus a tap anywhere on the text doesn't fall-through to its parent. Is there any way to make only the clickable regions of text consume the pointer events?

What’s the best way to accomplish this layout? I was thinking about using a

FlowRow

that contains the `Chip`s for each user, with a

TextField

that will fill remaining width? How would I get the

TextField

to fill the remaining width in the row while also having a minWidth?

Has support for marquee text been added lately? I know it wasn't supported as of about 6 month ago

Hi all, from the doc

<https://developer.android.com/guide/navigation/navigation-pass-data#supported_argument_types>

navigation can accept a nullable string as parameter. Should we ignore the null argument ?

Does anyone know if it's possible to programmatically determine what the current color is beneath/behind a composable? The scenario I'm trying to solve is that I want to composite a transparent overlay color on top of the background color and use the resulting composite color in order to create a cut-out appearance. For example, see the area around the check mark in the attached image. I, of course, can pass the background color to composite over into the composable, but that would require passing this down through several composables (which other than to pass it on, shouldn't need to know the background color).

Seeing a

has no zero argument constructor

runtime error when using

androidx.lifecycle.viewmodel.compose.viewModel()

🧵

I am facing an issue with displaying a copy-paste popup inside a Popup composable. My use-case is to display a text field inside our component, which uses Popup underneath. Text field works correctly, but when I try to copy-paste something application crashes. Is it even possible to “nest” popups? Tested with latest Compose 1.2.0-alpha02 & Kotlin 1.6.10, also reproduced in older versions. See video, code example and crash log in the 🧵. Thx for advice.

Hi! I know this may be a ... dummy question about texts, but I'm running out if ideas here. We have a chip, created by

Surface

and

Text

inside it, text is in a

Row

, centered both horizontal and vertical. We see a small pixel.. difference, as it should be on the center, and we see here that text is a bit under the center.. Any idea?

Is there a way to stick a

stickyHeader

not to top of

LazyColumn

but to top with some offset?

How to show only the fitting items in a row? do we have any modifiers for this. or should i write a custom layout for this.

is it possible to make view pager looped infinite?

Looks like Version 1.2.0-alpha02 of compose was release a few days ago A few interesting things I found: • Text selection magnifier behavior has been polished to match the platform magnifier. •

LazyColumn

, 

LazyRow

, 

Modifier.verticalScroll

 and other containers that use 

Modifier.scrollable

 now support mouse wheel scrolling. • Added 

excludeFromSystemGesture

 Modifiers for easy access to Android's 

setSystemGestureExclusionRects

  • Fix continuous backspace on CJK keyboards (I think this is the fix for continuous backspace not working in password fields 🤞) • Preserve scroll when items are added in lazy grid • Fix TextFieldKeyInput onValueChange (this seems to fix an issue of typing with your keyboard on an emulator) • Compose Material - Add support for action chip (not sure if this is a new chip component, but I want to check it out) • Added Material 3 divider • Added support for Material 3 progress indicators • Add experimental View.createLifecycleAwareRecomposer extension (idk what this is but it sounds interesting...) • Wear OS - Add support for Rotary Events modifiers

Is there a Modifier that lets me wrap the content that is about to be created in a CompositionLocalProvider. I.E. If i apply a modifier to a composable, I’d like the child content to be able to access that set CompositionLocal.

Hi. Anyone having problems rendering previews on BumbleBee? stacktrace on 🧵

New to Compose, but have done AWT, Swing, GWT, Web (of course), and interested in Fyne (GoLang), JavaFX. In the ones I've actually used, each "component" could access the "parent component" (walk the directed graph, e.g. DOM), is that possible with compose?

Hi all! I'm would like to create an AlertDialog with a scrollable content but I have a strange behavior with a padding in top of the dialog and the content that goes under my buttons in bottom of the dialog. There is already an issue created on the bugtracker somewhere about that?

Hi! How can I make all rows in collumn has the same width = longest row in column?

I'm using Compose in two repos -- one that is a small design system library and one very large monorepo that is organized into smaller modules. We've noticed that Compose previews are very slow in the monorepo. Has anyone dealt with this? Any tips for making previews faster in a large repo or know what specifically about a large repo causes this? We're currently using Bumblebee.