Hello! Using

detectTapGestures

how can i disallow user to pan/translate the content out of its bounding box? I have scale working with translations as well but the user is able to translate the image out of the screen. How can I set some limits for translation?

Is this a bug? Watch the scrollState.value go from 864 to 0 when the Row gets composed twice (for no obvious reason). This leads to the scroll position not being retained.

Hi everyone, happy Monday. Is there a best practice on using Custom Tabs with Compose Navigation? I currently have something like the following:

composable(...) {
  val context = LocalContext.current
  SideEffect {
    CustomTabsIntent.Builder().build().launchUrl(context, myUrl)
  }
}

I’ll be expanding on this a bit to warm up the browser, etc, but is this basically what I need to do? Call

launchUrl()

from inside the Composable?

The state is changing, but the recomposer doesn't update the TextNode, any solutions?

Having in mind a form with 10 fields (for instance) of different types (text, radio button, checkbox, combobox, … ). What do you folks think is the best approach? 1️⃣ Expose one `Flow`/`LiveData` for each field in ViewModel and collect/observe them individually in the screen. 2️⃣ Expose one

State

for each field in ViewModel and simply access them from the screen. 3️⃣ Encapsulate these 10 fields in a data class, expose one single `Flow`/`LiveData` and each “setter” create a

copy

of this data class instance to update the state. 4️⃣ Encapsulate these 10 fields in a data class, each field is a state, ViewModel has an instance of this class and you simply access it from the screen. 5️⃣ Other (please explain)

I am trying to add a centered loading indicator inside of LazyColumn like shown in the text snippets however, my loading view is never centered. I am guessing it has to do something with how the children of the lazy column are measured. Is there a way to have the loading view take up the rest of the screen so that I can center the circular progress indicator?

Why preview don't work ??

with the RC1

ui-tooling

split, is the following dependency declaration the "most correct" if I also need to annotate my composables with

@Preview

?

implementation("androidx.compose.ui:ui-tooling-preview:$compose_version")
debugImplementation("androidx.compose.ui:ui-tooling:$compose_version")

I filed this bug some time ago but it didn’t get very much attention, can somebody tell me if you are also experiencing this? https://issuetracker.google.com/issues/190423020 It affects both compose preview and xml layout preview. NB: when checking out the attached images make sure you zoom to 1:1 scale or you won’t notice the low res artifacts

Noticed that previews do not work when I use a viewModel in a composable. How do you get around this?

what is the best way to pre populate a textfield in compose but remember the following state?

Does anyone know, how to listen for lottie animation completed? Thanks!

If I have an inline (now

value

) class, can I mark it as

@Immutable

? Will this property transfer to the wrapped class and be understood accordingly by the Compose runtime later on?

Is it possible to intercept click event before child composable? For (bad) example, how would one intercept event on Column level, and not pass it to TextField, without making any changes to TextField:

Column(modifier = Modifier.clickable { Timber.d("click") }) {
    TextField(value = "smth", onValueChange = {})
}

Is there any indication yet whether next RC release will work with Kotlin 1.5.20? Running in to a few dependencies I need to pull in that only work with 1.5.20 (at least when using Kotlin/Native) and blocked as projects also use Compose.

Trying to wrap my head around pointer input. Can anyone explain why the first child is not clickable? Ideally with a link to source code. I'm not consuming touch events in the second child, I'm not even collecting them.

Box(Modifier.fillMaxSize()) {
    Box(Modifier.fillMaxSize().clickable { error("Yay!") })
    Box(Modifier.fillMaxSize().pointerInput(Unit) {})
}

I mean, even if parent Box decides that the second child should get events first (which is questionable, but okay), why does

pointerInput

block the flow?

Hi, since

Card

and Surface have the

onClick

parameter how can I define an

onLongClick

assuming that the code below does not work

Modifier.combinedClickable(
    onLongClick = {
      Timber.e("Long Click")
    }
)

Modifier.genericClickableWithoutGesture

that support

onLongClick

is marked as internal

What would be the best practice in jetpack compose to react to the application being paused, such as the user swapping to another application? This would be useful such as when the application is playing audio, you don't want the audio to continue playing when the app is in the background. I know we can override onPause() in the main activity, but how can we aim to let the rest of the application know that it is paused?

Should

ModalBottomSheetLayout

collapses when back key is pressed? 🤔

Hello everyone, after Compose Canvas draws a graph, can I add a click event to the point in it?

Has anyone seen

pending composition has not been applied

before? Stack trace in thread

Is anyone building a "pure" Compose app? • single activity • no fragments • no AndroidArchComponent ViewModel If so, are you creating your own ViewModel (plain kotlin class, that does not extend AAC ViewModel)? I think most people agreed that AAC ViewModel was a not so great name when it came out. What is your project calling the thing that keeps state + handles events?

How would you model a state emited from viewmodel/presenter, if you need to render a "Hello Joe"?

State(val greeting: String) and just render thr greeting

State(val name: String) render "Hello $state.name"

State(val user: User) render "Hello $state.user.name"

TLDR; do you format in viewmodel or in composables?

Does anyone know if Jetpack compose will allow configuration-driven UI easier? I’m working on a white label app and there are some differences between brands.

Why

AlertDialog

takes a full width with no horizontal padding by default?

Anyone had problems, when setting transparent background to Snackbar?

Hey everyone, Android studio has a code snippet to create a Box when you type W. Supposedly, it’s to facilitate wrapping composables. But how do you use it for wrapping?

Moreover, I think the concept of something being

@Immutable

is useful outside of just Compose.

Is it possible to get the accumulated scroll offset from a

LazyListState

?