Is it correct that

.pointerInput(Unit) {}

can only take one argument? I have one call to

detectTransformGestures

, but if I add another thing like

detectTapGestures(
    onPress = {
        println("ON PRESS")
    }
)

or

detectDragGestures

before that it's never called. Only the first of these are called and all others are ignored. I don't know how I'm supposed to combine a drag handler with a pinch-zoom detection... The "pan" does not help me, because I don't know when the drag is ended (the finger lifted).

Any plan in restoring Data Table now that Compose has stabilized? it has been removed long ago https://android-review.googlesource.com/c/platform/frameworks/support/+/1276360

I've seen a good practice of Jetpack Compose that is to group Composable methods inside Objects, but never managed to use it because of one problem.

object ButtonActionBar {   
    @Composable
    fun RowScope.CancelButton(onClick: () -> Unit) {
        Button(
            modifier = Modifier.weight(2f),
            onClick = onClick
        ) {
            Text(
                text = "Cancel"
            )
        }
    }
}

@Composable
fun RowScope.PublishButton(onClick: () -> Unit) {
    Button(
        modifier = Modifier.weight(2f),
        onClick = onClick
    ) {
        Text(
            text = "Publish"
        )
    }
}

Row(
   modifier = Modifier.height(48.dp)
) {
   SessionActionBar.CancelButton() {}
   PublishButton {}
}

In this example the

PublishButton

work fine but not the

CancelButton

, if I remove the

RowScope

it kinda work (but then I don't have access to

weight

modifier) or need to move it outside of

ButtonActionBar

object as the

PublishButton

I have a high-level TextField component:

fun OurTextField(modifier: Modifier) {
   Column(modifier) {
     Label()
     TextField()
     ErrorMessage()
   }
}

So when our devs use it in UI tests, they pass testTag that is in the Column's modifier. However, that breaks the bahavior, especially for setting a value to text field. (There is no SetText on Column). What is the best solution for those high-level components: • merge tree on column (something which will work nicely for SetText, worse for other texts; alternatively reexpose them - Text for input, new semantics for Label and Error) • exposing tag names which ui tests may reused to specify "child" of the OurTextField • do nothing and let ui tests to use onChildAt(1) to get access to TextField • some other approach?

Hi there!! I’m facing one issue when testing one screen that I just migrated to compose.. and I’ve created this small playground project to reduce the scope and to point out the specific issue hoping for some help!! Issue is about adding

verticalScroll

behaviour to a Column.. compose needs be idle in order to proceed.. but when verticalScroll is in place, test is stuck doing something:

2022-03-14 17:52:52.078 16637-16651/com.compose.playground I/pose.playgroun: Background concurrent copying GC freed 633159(22MB) AllocSpace objects, 1(20KB) LOS objects, 49% free, 4055KB/8110KB, paused 371us total 798.298ms

https://github.com/danimontoya/compose-playground/commit/74bf12fc5c9df9118602ab3a1989cef618f6b005 I would like to keep the veticalScroll behaviour and the tests on that screen not stuck and green, as it works for phones (only happens on tablets == master/detail fragments).. any pointer whats going on?? thanks in advance 🙂

Hey everyone, I have a question about compose ripples. I have a Radio button in a row, and when the row or button is selected, I want the ripple to show in the entire row. Currently I have that working, except when they click on the radio button itself, when they do that it shows the circular ripple around the radio button. I can disable that ripple with a dummy interaction source, but then I get no row ripple. How can I make it so when they click the radio button it ripples for the whole row?

I’m using Navigation Compose and some of the destinations in my graph use

AndroidViewBinding

to load a

FragmentContainerView

with “legacy” fragments (until we can get them converted to compose):

composable(route="my-screen") { AndroidViewBinding(MyFragmentBinding::inflate) }

What I’m struggling with is … when some action is taken in the Fragment (like say a button is clicked), I need to navigate to a new destination (route). How can I do that?

When wrapping a

WebView

in an

AndroidView

for use in a compose app, I have need of methods on the webview instance outside of the wrapped component for example a refresh button that calls

webView.loadUrl(…)

. How do I expose this to composable functions using the

WebView

component? Unsure how to expose this from the wrapped component

In VSCode / Flutter, there is a really nice “Wrap with new Widget” feature where you don’t need to select your whole Widget, but just have your cursor on the Widget to be wrapped. Does this exist for Android Studio / Compose too? Now, I have to select the Composable and all of its contents and then wrap it. It would be nice to skip selecting everything every time.

I have`ExposedDropdownMenuBox` and nested

OutlinedTextField

. Initial

ExposedDropdownMenu

contains nested

TextField

. I am unable to open keyboard when nested

TextField

is focused. How do I enable keyboard on nested

TextField

?

Hey Everyone 😄, I have a question about getting xml resources,

fun dimensionResource(@DimenRes id: Int): Dp

returns DP dimensions, but there’s no SP version of it, is there a way to return the SP xml dimensions?

Hi! I have a LazyColumn and want to change the screen-background-color to that of the item-background at the center-position. It's working fine I'm not sure if I do the calculations at the right place because as soon as I add those calculations I'm triggering infinite recomposition thats why I think I do something wrong. Code-Example in Thread.

Hello everyone! I've been researching about how to change/remove the dimming/scrim in the Dialog composable. I've found some outdated solutions in the chat history and this ticket in the issue tracker: https://issuetracker.google.com/issues/159900354 but I do not know how to proceed with this. Is there a way to do it without re-implementing the whole thing? If re-implementation is needed what exactly needs to be changed? I cannot find in the Dialog Composable code where the dimming effect is being applied.

Hi! I am working on a stock trading application and we are currently migrating our real-time updated lists to compose. I have a

LazyColumn

witch displays the stocks and each stock is real-time updated through web-socket events. I am testing the LazyColumn performance (using a release build) and it’s dropping frames. The performance is not as good as it was with the RecyclerView (with DiffUtil). I also used the Recomposition highlighter from the Google play team and verified that my LazyColumn is constantly recomposing. I will include the code in the thread. Any ideas on how to improve the performance?

How can i solve this exception with my navGraphs on orientation change? I do not get this error when top/starting navGraph.

java.lang.IllegalStateException: Restoring the Navigation back stack failed: destination -1666506032 cannot be found from the current destination Destination(0xcf551cdb) route=SettingsNavGraph

Is there any way to see visually when a recomposition occurs just for checking that you’re not doing unnecessary recomposition? some sort of inspector or debug option?

Why one `TextField()`'s boolean argument is named

isError

and another without

is

-

readOnly

?

Is there a way to scope an AndroidX View Model to a composable, or does that even make sense? AFAICT, when injecting through `viewModel()`/`hiltViewModel()`, the VM is scoped to a

ViewModelStoreOwner

, which might be a nav back stack entry or a fragment or whatnot, but not an “actual” composable, if that makes sense. However, if I have a list of similar items and I want each of them to have their own instance of a same-type View Model, then I'm at a loss on how to achieve this. Any suggestions?

Can anyone please share any references regarding compose navigation in dynamic feature modules?

I have a question regarding surface. When I wrap a parent-composable in a surface it applies my theme standard values (like color e.g.). But when I place a child-composable inside parent composable those values are not adopted in the child. I also need to wrap the child in surface. Is this expected behaviour or how should I deal with it?

Is there a way to report a value change in the example below assuming I have no way to modify

State

?

class State(
  val value by mutableStateOf(false)
)

fun Component(state: State, reportValueChange: (Boolean) -> Unit)) {
  val v = state.value 
  // how to call reportValueChange(v) here
  // **only** when "v" changes?
}

I have tried

snapshotFlow { state.value }.collect(::reportValueChange)

but it emits nothing on value changes

Is there something in Material 3, to combine Material Extensions with Dark mode. In Material 2, it was like this:

val ColorScheme.link: Color
    get() = if(isLight) colorX else colorY

But, this doesn’t work with M3?

Some composables (swipeable, BottomSheet*, HorizontalPager, LazyColumn etc) have some internal state which they manage by themselves and even when this state is allowed to be hoisted the need for detecting some events based on state changes arises. I find myself wishing to write

if (prevState = 1 && state = 0) onEvent(...)

. Sometimes this leads me to discovery that I think about the state wrong and I refactor, but sometimes I can't and I ask myself what's the best pattern to detect some thresholds in state changes? Examples: • ListColumn has just scrolled past 100 visible item, how to report this to analytics? • Composable with

swipeable

modifier has just finished settling after swipe. How to observe this change from

swipeableState.isAnimationRunning

from

true

to

false

and report it to some other component?

Hello all! I want to keep my toolbar always on the top and navigate screens under of it in fully compose project. I couldn’t find a way for this, do you have idea? Normally it can be done like this in XML way:

<?xml version="1.0" encoding="utf-8"?>
<androidx.constraintlayout.widget.ConstraintLayout xmlns:android="<http://schemas.android.com/apk/res/android>"
    xmlns:app="<http://schemas.android.com/apk/res-auto>"
    android:layout_width="match_parent"
    android:layout_height="match_parent">

    <androidx.appcompat.widget.Toolbar
        android:id="@+id/toolbar"
        android:layout_width="0dp"
        android:layout_height="wrap_content"
        app:layout_constraintEnd_toEndOf="parent"
        app:layout_constraintStart_toStartOf="parent"
        app:layout_constraintTop_toTopOf="parent" />

    <androidx.fragment.app.FragmentContainerView
        android:layout_width="0dp"
        android:layout_height="0dp"
        app:defaultNavHost="true"
        app:layout_constraintBottom_toBottomOf="parent"
        app:layout_constraintEnd_toEndOf="parent"
        app:layout_constraintStart_toStartOf="parent"
        app:layout_constraintTop_toBottomOf="@id/toolbar"
        app:navGraph="@navigation/nav_graph" />

</androidx.constraintlayout.widget.ConstraintLayout>

Getting an exception when using

bottomSheet

from accompanist:

java.lang.IllegalArgumentException: The target value must have an associated anchor.
    at androidx.compose.material.SwipeableState$snapTo$$inlined$collect$1.emit(Collect.kt:136)
    at kotlinx.coroutines.flow.FlowKt__LimitKt.emitAbort$FlowKt__LimitKt(Limit.kt:73)
    at kotlinx.coroutines.flow.FlowKt__LimitKt.access$emitAbort$FlowKt__LimitKt(Limit.kt:1)
    at kotlinx.coroutines.flow.FlowKt__LimitKt$take$2$1.emit(Limit.kt:63)
    at androidx.compose.material.SwipeableState$special$$inlined$filter$1$2.emit(Collect.kt:137)
    at kotlinx.coroutines.flow.internal.SafeCollectorKt$emitFun$1.invoke(SafeCollector.kt:15)
    at kotlinx.coroutines.flow.internal.SafeCollectorKt$emitFun$1.invoke(SafeCollector.kt:15)
    at kotlinx.coroutines.flow.internal.SafeCollector.emit(SafeCollector.kt:77)
    at kotlinx.coroutines.flow.internal.SafeCollector.emit(SafeCollector.kt:59)
    at androidx.compose.runtime.SnapshotStateKt__SnapshotFlowKt$snapshotFlow$1.invokeSuspend(SnapshotFlow.kt:134)
    at androidx.compose.runtime.SnapshotStateKt__SnapshotFlowKt$snapshotFlow$1.invoke(Unknown Source:8)
    at androidx.compose.runtime.SnapshotStateKt__SnapshotFlowKt$snapshotFlow$1.invoke(Unknown Source:4)
    at kotlinx.coroutines.flow.SafeFlow.collectSafely(Builders.kt:61)
    at kotlinx.coroutines.flow.AbstractFlow.collect(Flow.kt:227)
    at androidx.compose.material.SwipeableState$special$$inlined$filter$1.collect(SafeCollector.common.kt:114)
    at kotlinx.coroutines.flow.FlowKt__LimitKt$take$$inlined$unsafeFlow$1.collect(SafeCollector.common.kt:115)
    at androidx.compose.material.SwipeableState.snapTo(Swipeable.kt:943)
    at com.google.accompanist.navigation.material.SheetContentHostKt.internalHide(SheetContentHost.kt:188)
    at com.google.accompanist.navigation.material.SheetContentHostKt.access$internalHide(SheetContentHost.kt:1)
    at com.google.accompanist.navigation.material.SheetContentHostKt$SheetContentHost$2$2$1.invokeSuspend(SheetContentHost.kt:145)
    at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
    at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
    at androidx.compose.ui.platform.AndroidUiDispatcher.performTrampolineDispatch(AndroidUiDispatcher.android.kt:81)
    at androidx.compose.ui.platform.AndroidUiDispatcher.access$performTrampolineDispatch(AndroidUiDispatcher.android.kt:41)
    at androidx.compose.ui.platform.AndroidUiDispatcher$dispatchCallback$1.run(AndroidUiDispatcher.android.kt:57)
    at android.os.Handler.handleCallback(Handler.java:938)
    at android.os.Handler.dispatchMessage(Handler.java:99)
    at android.os.Looper.loop(Looper.java:246)
    at android.app.ActivityThread.main(ActivityThread.java:8633)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:602)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1130)

How should I fix this up? As per this SO question, the fix should be by mentioning the minHeight as 1 dp: https://stackoverflow.com/questions/68623965/jetpack-compose-modalbottomsheetlayout-throws-java-lang-illegalargumentexception But this solution doesn't work for me.

How can you fill a row with two buttons: First button should take the max width, but there should be another minified button.

@Composable
fun InfoButton(infoTest: String, button: @Composable (Modifier) -> Unit) {
    Row(modifier = Modifier.fillMaxWidth()) {
        Info(infoTest)
        button(Modifier.fillMaxWidth())
    }
}

This code renders the icon at the left side, I want to show them on the right side

Hi folks 👋, This question is regarding benchmarking composables in Jetpack Compose. What I am interested in as a starter is to measure how long does it take to render a composable on a screen for the first time it is composed and on recompositions. What I have tried so far: • Android benchmarking samples from the official repo here. • Looked at other initiatives that folks in the community have come up with like this repo here. • I took suggestion from @romainguy on this thread , @Leland Richardson [G] on this thread and went about trying out how can I utilize some of the ideas there. There are many good starting points for benchmarking in the compose repo. I found something that seems very relevant in tests for

Text

composable in TextBasicBenchmark that uses ComposeBenchmarkRule. It uses a few methods that benchmarks the first composition, measure, draw, layout. The problem I am running into is what how would I be able to use that ComposeBenchmarkRule? I couldnt find any dependencies/library that exposes this class. Is this currently available for use in any jetpack compose testing libraries? How should I go about it? Thanks for creating this space and allowing the questions to be asked. Much appreciated 🙌

Hi folks. Is there any composable or any custom solution to handle text line-break and hyphenation? Any plans to support hyphenation in compose in the future?

About Text: Is it expected that the app will handle all focus manually for Keyboard actions such as

onNext

to

Focus.DOWN

for example, or will it be handled by Compose? • Software Keyboard Next, Enter • Hardware Keyboard Tab, Shift+Tab, Enter