Is there a way to show items in a row and overflow to a new line? or I need to create a view to do that?

Is there any way to measure a Composable before drawing without getting the siize aferward with .onSizeChanged?

Is there a way to react to the progress of AnimatedVisibility? My use case is that I have a list of composable functions, and I want to animate additions and deletions to it, so I'm wrapping each item in an AnimatedVisibility. The problem as I understand it is that I can't delete a function from the list until the transition is finished (because then it won't get composed anymore; is that the proper terminology?). My idea is to mark the item as deleted, and remove it once the transition is complete, but I'm not 100% sure how to do that.

Has anyone run into this? I posted it on Stack Overflow a couple weeks ago and nobody had anything to say https://stackoverflow.com/questions/66126551/jetpack-compose-centering-text-without-font-padding

Hello! My team has a custom type scale and therefore we're not using the material type system. Is there anything wrong with this code or is this pretty much how you set it up?

private val Lato = FontFamily(
    Font(R.font.lato_regular, FontWeight.Normal),
    Font(R.font.lato_bold, FontWeight.Bold),
)

object MyTypeSystem {
    val head = TextStyle(
        fontFamily = Lato,
        fontSize = 18.sp,
        fontWeight = FontWeight.Normal
    )
    val body = TextStyle(
        fontFamily = Lato,
        fontSize = 12.sp,
        fontWeight = FontWeight.Bold
    )
...
}

Is there a way to

remember

something mutable, but not cause a recomposition when it is mutated?

Is there a way to capture (any) touch event at parent level, so that child composables are not reacting to it?

loadImageResource is deprecated since alpha12. What’s the proper replacement? Does painterResource load the image in background?

I'm trying to use popUpTo with Navigating with Compose.

popUpTo(Destination.OnboardingWelcomeScreen.route) { inclusive = true }

But it giving me error because it's expecting int instead of String.

Hi all, I’m wondering if there are any good examples out there showing how to load things off the main thread from inside a composable

My use case is: I pass a ResolveInfo object to my composable function and load an app name and icon from inside that composable, at the moment it’s super slow

Is there a way in LazyColumn to scroll to a particular position in an Item. I'm working on building Expandable Item List. And each Expandable Card contains multiple Questions that user has to fill the answer. Once the user submit the answer, I check the validations from server and show the error is respective answer. Now i need a way to scroll to that particular answer and then keep on moving to the next error. Before COMPOSE i used to do this via requestFocus using a recyclerview. i have been going through documentation of compose and unable to find a way to build this

I understand that there is a way to scroll to the item, but nothing if need to scroll to a particular content in that item(Expandable vIEW)

Why

onCommit

crashed with

Composition re quires an active composition context

?

@Composable
fun NetworkImage(
		modifier: Modifier,
		url: String?,
		placeholder: Int
) {
		var image by remember { mutableStateOf<ImageBitmap?>(null) }

		onCommit {
				val picasso = Picasso.get()

Hi, is there a way to add listener to

Transition

? I'd like to do an action after the new state have been reached something like:

val transitionState = remember {
    MutableTransitionState(false)
}

val transition = updateTransition(transitionState)
val scale by transition.animateFloat(
    transitionSpec = { spring(dampingRatio = Spring.DampingRatioMediumBouncy) }
) {
    when (it) {
        true -> 1f
        false -> 0f
    }
}

LaunchedEffect(viewModel, navController) {
   delay(1000)
   transitionState.targetState = true
   // Then I want to do an action after the animation finished
   // but I can't find a way to attached a listener to Transition.
}

Hi, I am working on some functionality in our application that requires the render of single-stroke fonts for cutting. Unfortunately android cannot display such fonts correctly, so we use the

Freetype Harfbazz

library to render individual glyphs as a sequence of vector paths. Now I'm looking for an option how this can be integrated into the pipeline of the standard android input system, and with the Compose(I'm considering CoreTextField). In the case of working with a regular

EditText

, it seems to me that I will need to rewrite everything from scratch(cursor, line break, context menu, text selection, etc.). But since the Compose has platform(android, desktop) implementations of text input, that means it uses abstractions around working with text. Which means it is should be possible to change implementation. I found an abstraction like Paragraph and its platform implementation for Android AndroidParagraph, which under the hood uses the TextLayout wrapper for StaticLayout class. And a MultiParagraph class that uses the above Paragraph. I would like to replace the implementation for the

AndroidParagraph

with my own but it seems that I do not see how this could be done. I would be apprecited any help. Thanks.

Animation APIs in Compose seem very complicated. I literally don't understand any of what the inline docs say!

I realized there is a lot of confusion about the concept of “*Single Source Of Truth*”. In traditional Android development, we used to talk about SSoT in the context of the Repository. Can we please agree, and probably make it clear, that the SSoT in the context of JetpackCompose (and DeclarativeUIs), has nothing to do with the Repository (and the DataLayer), but only with the ViewModel? I keep hearing developers saying that the SSoT of an app is the DB, even in the context of JetpackCompose. How does that make sense? I am attaching a diagram, where I try to highlight the difference between AppState (which is part of the ViewModel) and Repository (which is part of the DataLayer), with particular reference to the D-KMP architecture. Any comment is very welcome.

it seams that

rememberSaveableStateHolder

is broken in somehow in alpha12. Consider example from here: https://github.com/androidx/androidx/blob/androidx-main/compose/runtime/runtime-sa[…]/compose/runtime/saveable/samples/SaveableStateHolderSamples.kt and change

Box(modifier) {
            restorableStateHolder.SaveableStateProvider(currentScreen) {
                content(currentScreen)
            }
       }

to

Box(modifier) {
            restorableStateHolder.SaveableStateProvider(currentScreen) {
                Crossfade(targetState = currentScreen) {
                    content(it)
                }
            }
        }

you will notice that animation doesn’t work. If you will remove that state holder:

Box(modifier) {
            Crossfade(targetState = currentScreen) {
                content(it)
            }
        }

crossfade works. So either

stateholder

is broken or

crossfade

. From what I unsderstand problem is that Crossfade implementation uses

remember

to store items to render during transition. What I wanted to achieve is some nice animation between screens. What to do? 🤔 🙀

I've implemented custom Pager based on this implementation, but also supporting zoom and vertical pan for alpha11. In alpha12

DragObserver

got deprecated, but I didn't manage to properly migrate my implementation to new API. Using two

draggable

modifiers prevents from dragging simultaneously in both directions and zooming at the same time, while using

pointerInput

lacks was kind of tricky: •

detectDragGestures

lack

onStart

and

velocity

parameter in

onEnd

callback •

drag

function seems to allow more fine-grained setting up, but judging by

detectDragGestures

is also quite hard to handle. Also

velocity

has to be calculated somehow (isn't really clear) I'll attach deprecated snippet, which I currently use, and would be glad to know several directions on how it can be implemented with new API with the similar amount of code.

Hi, my BasicTextField composable and

adjustPan

are not behaving properly after the first focus. The first click, the composable is properly moved up but if you close the keyboard and click back into the field, it is now partially obscured by the keyboard. Has anyone run into this?

How I can do clickable inside of

items

for

LazyColumn

?

having a rough time trying to get started with 0.3.0 in the tutorials

Is there a way to update the variables without directly reorganizing them?

remember { mutableStateOf(...) }

will be reorganized immediately after each

setValue

, but I just want to update the variable, and then manually reorganize and remember this variable at some point. what should I do?

Everybody is waiting beta 😉

If a sealed class is marked as

Immutable

are all of its subclasses considered

Immutable

as well?

Any recommendations for an implementation of Collapsible App bar in compose please?

Any idea how to create viewmodel scoped to composable function, means it will be destroyed once the function disposes.

Is anybody else also stuck with text not being vertically center in buttons, top app bar, etc? Seems a bit towards the top than center.