Setting isInteractive = false to the view still consumes events

[alexstyl]

I would like to be able to set interactivity modifiers to SnizzorsUIView so that I can move the view around with touch gestures.

It seems like even if I set interactivity to false, the UiKitView still consumes the events.

It would be great to be great to be able to use it. Potentially possible to make proper use of Liquid Glass with this technique.

My code:

@Composable
fun InteractiveView() {
    var offsetX by remember { mutableStateOf(0f) }
    var offsetY by remember { mutableStateOf(0f) }
    SnizzorsUIView(
//    UIKitView(
        properties = UIKitInteropProperties(
            isInteractive = false,
            isNativeAccessibilityEnabled = false
        ),
        modifier = Modifier
            .offset { IntOffset(offsetX.roundToInt(), offsetY.roundToInt()) }
            .pointerInput(Unit) {
                detectDragGestures { change, dragAmount ->
                    change.consume()
                    offsetX += dragAmount.x
                    offsetY += dragAmount.y
                }
            }.border(1.dp, Color.Red).size(48.dp),
        factory = {
            UIVisualEffectView()
        }
    )
}

PS: If i replace the SnizzorsUIView with UIKitView interactivity works, but then I lose the transparency.

[EricKuck]

This is a good catch! Unfortunately I'm not sure what can be done about this one. The isInteractive flag works with UIKitView because the compose content is on top of the UIKit content, which means compose automatically intercepts all touches, then forwards them to the UIKit component if and only if isInteractive is true.

When the UIKit content is on top, however, it receives user interaction events first. This leaves compose modifiers no opportunity to influence touch handling.

There are some possible workarounds, including adding touch handling in the UIKit layer, then forwarding those to compose. I'm very open to any ideas you might have on how this could be handled a bit more intuitively!