I am trying to make a child composable non-interactive under certain conditions. I don’t know anything about the child composable and can’t change its definition either(so can’t simply pass a modifier to it). So I was trying to wrap it inside a Box and then applying the

rawPressStartGestureFilter

to it. This actually works but it also ends up interfering with the scroll of the screen that these composables are on (this is expected as this is how you’d expect this gesture filter to work). Is there a better way to accomplish this? Just using

tap

or

clickable

on the parent composable still propagates the touch to the child composable so I need a better way to intercept the touch while keeping the scroll functionality intact.

I’m doing a progress view on top of all children maybe that can help:

Stack(Modifier.fillMaxSize()) {
        children?.invoke()
        Box(
            modifier = Modifier.fillMaxSize().tapGestureFilter {},
            backgroundColor = colorResource(id = R.color.transparent_black),
            gravity = ContentGravity.Center
        ) {
            CircularProgressIndicator()
        }
    }

oh that’s an interesting idea! Let me try stacking them!

If the most top box catches the tap, the children behind can’t be tapped on

With the same logic, I was trying this

Box(modifier = Modifier.clickable{ //do Something }) {
    child()
}

It’s possible that this does not create an “gesture hierarchy” of sorts but Stack does? Do you happen to know?

Box is just a container AFAIK, when Stack really puts the children one on top of another so that’s why it works

So for me to get it to work with Stack, I need to know the size of the child composable so that I can place a Box on top of it exactly using Stack. So I made use of the

onPositioned

modifier but the size it returns is incorrect and it ends up occupying a lot more space than the space the child composable occupies.

Stack {
    var size by state{ IntSize(0, 0) }
    Box(Modifier.onPositioned{size = it.size}) {
        childComposable
    }
    
    // Height it returns is almost double of what the child composable occupies.
    Box(Modifier.height(it.size.dp))
}

I haven’t, but i haven’t played with it for a while. I think there’s also currently a bug where only one

onPositioned

callback will be fired if multiple nodes are re-layed out, so there are clearly bugs. I’d suggest filing a bug.

Thanks for the super prompt reply! Yeah does seem like a bug! I’ll file it!