Hello 👋 Is there a way to intercept touch events such as

ACTION_DOWN

and

ACTION_UP

but still allow a LazyColumn to have

ACTION_MOVE

for scroll? My use case is: I want to allow a full screen list to scroll, but I want to do something when a finger is lifted up such as snap the list to a specific position

Anyone faced an issue with

accompanist

library and

hiltAggregateDepsDebug

* What went wrong:
Execution failed for task ':app:hiltAggregateDepsDebug'.
> Could not resolve all files for configuration ':app:hiltCompileOnlyDebug'.
   > Could not resolve io.github.aakira:napier:1.4.1.
     Required by:
         project :app > com.google.accompanist:accompanist-permissions:0.18.0
         project :app > com.google.accompanist:accompanist-pager:0.18.0
      > The consumer was configured to find attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug'. However we cannot choose between the following variants of io.github.aakira:napier:1.4.1:
          - commonMainMetadataElements-published
          - debugApiElements-published
          - debugRuntimeElements-published
          - iosArm64ApiElements-published
          - iosArm64MetadataElements-published
          - iosX64ApiElements-published
          - iosX64MetadataElements-published
          - jsApiElements-published
          - jsRuntimeElements-published
          - jvmApiElements-published
          - jvmRuntimeElements-published
          - metadataApiElements-published

if i want to draw a fixed size colored rectangle, with a logo inside. Should i use an image inside a box? surface ? other? i never know

Hi, Sort of following up attached question if one of the compose team has a sec? What would be the correct way to scroll down a lazy list using the dPad? Is there an issue I should watch where this would end up as part of the focus system, similar to how non lazy lists do it. (haven’t been able to find exactly what I was looking for)? Or should I capture dpad events and use lazy list animate to item function? Thanks a tonne! https://kotlinlang.slack.com/archives/CJLTWPH7S/p1632370300307400

Hey… I’m implementing Accessibility Tests with Compose and so far the only way that I’ve found to do is using ComposeRule and Semantics. I tried to cover more Accessibility tests like contrast, spacing, etc, with Espresso, by enabling

AccessibilityChecks.enable()

. However I noticed the View Hierarchy printed from Espresso only had a

ComposeView

and

AndroidComposeView

with no extra information like text, content description.

+---->AndroidComposeView{id=-1, visibility=VISIBLE, width=1080, height=1808, has-focus=false, has-focusable=true, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=true, is-layout-requested=false, is-selected=false, layout-params=android.view.ViewGroup$LayoutParams@6460a4, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=1} 
|
+----->RippleContainer{id=-1, visibility=VISIBLE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=android.view.ViewGroup$LayoutParams@ef261c2, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0, child-count=1} 
|
+------>RippleHostView{id=-1, visibility=VISIBLE, width=0, height=0, has-focus=false, has-focusable=false, has-window-focus=true, is-clickable=false, is-enabled=true, is-focused=false, is-focusable=false, is-layout-requested=true, is-selected=false, layout-params=android.view.ViewGroup$LayoutParams@508ebd3, tag=null, root-is-layout-requested=false, has-input-connection=false, x=0.0, y=0.0}

Another issue I had migrating to Compose is that our Espresso tests will fail after a simple screen migration. 😐 If we have a simple screen with just a Text. And we migrate to Compose, Espresso won’t find that Text anymore. So, just creating an Activity with a Text, and changing that to ComposeView and adding a Compose Text (with the same information). If we try to do the following code, it won’t find the View.

Espresso.onView(withText(R.string.app_intro)).check(matches(isDisplayed()))

I found this answer, so I guess I have to implement new tests while migrating to compose: https://github.com/android/compose-samples/commit/a6907c5dc236e9c18f062c44453b1c15359962cf#commitcomment-51521777 ---------- So, after this huge text, I have 2 questions 😬 1. Will Compose Semantics Test or Test libraries have something similar to Espresso

AccessibilityChecks.enable()

? 2. How can I check colors, images and other components properties like Modifiers/borders? These are not visible with SemanticsNode using Jetpack Compose tests. a. Right now I’m having to check with Snapshots (then some workarounds on top of Snapshot to work across different APIs)

is it possible to set text to always occupy at least 2 lines ?

Is there a ready to use Composable to draw line separators between list items? Or should we just use a Box with a very small height?

Is there any example on coordinator pattern in navigation compose

is there any variation of LaunchedEffect(boolean) that will only run when it is true?. Using a boolean works, but then the scope is restarted in true -> false. I have nothing to do on false so it seems quite a waste

We created a custom shape for a slideOver composable. When using the

Modifier.clip

the composable is shaped correctly but the inner content of the composable disappears in one of the screens where we use the composable. Could it be that composable interferes with the 

Modifier.graphicsLayer

 used in other screens?

Has anyone else used the accompanist animated navigation? I have the following (along with a rememberAnimatedNavController)

AnimatedNavHost(
    navController = navController,
    startDestination = router.currentStep.id,
    exitTransition = { _, _ ->
        slideOutOfContainer(
            AnimatedContentScope.SlideDirection.Left,
            animationSpec = tween(700)
        )
    },
    enterTransition = { _, _ ->
        slideIntoContainer(
            AnimatedContentScope.SlideDirection.Left,
            animationSpec = tween(700)
        )
    })

However, not a single one of my transitions is animated. It all still seems to just pop in and out like it would with the standard NavHost. (as a side note, i’ve tried putting animation specs in the composable function as well for the individual routes with no luck.

is there any standard practice for conditional modifiers inside a composable? Something like this:

modifier.run { 
    if(featureA){
        modifierX()
    } else{
        this
    }
}

My app needs to spawn a long-living process (that follows the app lifetime) and it has to communicate with it using stdin/stdout/stderr. I wanted to go full-compose, but it seems that it's still not possible to

rememberSaveable

a

Parcelable

(I need it to encapsulate the

Process

object); should I just declare an

object

at this point?

navigating back and forth between two composable fragments sometimes cause a ‘lag’ navigating back and i narrowed it down to this composable:

Image(
    modifier = Modifier
        .fillMaxSize(),
    painter = painterResource(id = state.itemList[page].imageRes),
    contentDescription = null,
    contentScale = ContentScale.Crop
)

This is loading a webp image. Maybe it is related to the image size. But most of the times it has no lag. What could it be ?

Hi, I'm trying to make a dashboard like in the attached image. Nothing really needs to be scrollable aside from the main display. However, I keep getting this error:

Nesting scrollable in the same direction layouts like LazyColumn and Column(Modifier.verticalScroll()) is not allowed. If you want to add a header before the list of items please take a look on LazyColumn component which has a DSL api which allows to first add a header via item() function and then the list of items via items()

Anyone have an idea for how I can add the grid pressure display inside a column of rows that arranges the displays?

Hi. Can we use Java or Kotlin libraries (libraries that use XML to design) in the Android JetpackCompose project? And how can we do it?

I have some issues using the

Modifier.clip

to apply a custom shape when there is an

Image

composable + bitmap somewhere in the view (separated from the shape). The clipped shape disappears when the bitmap reaches a certain size or multiple bitmaps in the view reach a certain combined size. Though the limits can differ on different devices.

Hi everyone, Is it possible to use SavedStateHandle in ViewModel with navigation compose?

Is there a way to “disable” (as in “grey out and don’t allow interaction with”) an entire UI subtree? I was thinking via a modifier at the root of the subtree or a CompositionLocal but I’m not aware of any.

Has anybody here seen an open-source example of using Compose to drive a non-UI tree?

is it possible to identify if a composable fun is running on preview or device ? some code need fake config for preview only

bold xml tags on strings are not supported yet for text, are they:

<b>

?

How I can trigger a piece of code only in the initial composition inside a function?

I have a strange click through issue when clicks are sent to the view under the visible one see code in thread. Are there known issue like that?

Any opinions on https://github.com/google/accompanist/issues/729 (offering the possibility for animated navigation transitions with a single

NavHost

)? Should I report an issue on the Google Issue Tracker instead?

if i were to make my own textinputlayout component, what base textfield component would i use? I don’t need error, border, etc

Can someone point me at an example of infinite scrolling a LazyColumn that doesn't use the paging library? (more of what I've tried in the thread)

do modifiers apply full recomposition of the composable they belong to? For instance, imagine a modifier with a border, with a mutableState as color ?

Is there an easy (and inexpensive, effortless) way to draw row elements from the last one? My

ReverseRow

code in thread