Blur happens also in children about haze

[chrisbanes]

Is the SurfaceView underneath disrupting the modifier?

Not sure, but I don't believe so.

Is it even possible to do it with haze? can you exclude children composables?

No, the haze and hazeChild need to be siblings and not descendants of each other, otherwise the child will be blurred, as you've found. I assume that the Box is a child of the BoxWithConstraints?

[chrisbanes]

Closing this as working as intended. Feel free to comment if there's anything else.

[KirkBushman]

@chrisbanes I tried to put the haze and hazeChild element next to each other, but it didn't work. I'm trying to make the haze effect take the colours from an active RTC video feed but make it fully transparent. There seems to be an issue with a setup using an AndroidView/SurfaceView. :((

I might have to give up on it and use an opaque colour instead.

Here below my setup:

AndroidView(
    factory = { context ->
        val frameLayout = FrameLayout(context)
        val surfaceView = videoRenderHelper.setupRemoteVideo(
            uid = partner.id,
            renderMode = videoSizeHelper.calculateRenderMode(state, uiState, agoraState),
        )
        frameLayout.addView(surfaceView, 0)
        frameLayout
    },
    modifier = Modifier
         .haze(
              state = hazeState,
              backgroundColor = MyTheme.colors.backgroundControls,
         )
    )
}

Also, I think that having the .haze() and .hazeChild() composables always as siblings is pretty limiting. It makes it difficult to use in cases when you need AnimatedVisibility... or any custom composable that wraps your blurred item.

Could the HazeState be changed in the future to remember the references to the background and child, so it can be used in a nested way?

Thank you in advance for your help,
and for creating this library.

[chrisbanes]

Simple answer, no. It's just the way that Haze needs to work. We're basically doing our own (very limited) window layering, and I don't plan on doing anything more complex.

[KirkBushman]

@chrisbanes I thought so, thanks anyway for your work. I think this is still a great library for simpler use cases. 😃