Hello! How do I handle click event without consumi...

# compose-desktop

[Lamberto Basti]

Hello! How do I handle click event without consuming them? Say that you have a Box with a such modifier to intercept the clicks and do stuff, but I want the content of the box to also receive the clicks!

[Lamberto Basti]

@Igor Demin :3

[Igor Demin]

There is no a high-level modifier for that (clickable or onClick). But you can add Modifier.pointerInput to the Box and react to events, without consuming them (event.consume() is called by clickable or onClick, for example)

[Pablichjenkov]

I had a similar one, here:
https://kotlinlang.slack.com/archives/CJLTWPH7S/p1677561456829879
The closest I got was Modifier.nestedScroll(connection, dispatcher) but still, the parent event dispatching worked when the Parent composable is a Pager but not when it is a NavigationDrawer.
Perhaps we need a modifier similar Android Modifier.pointerInteropFilter, it gives you the chance to get the event stream and participate/not-participate in the consumption by returning true/false in the dispatching function/lambda.

[Pablichjenkov]

Using Modifier.pointerInput and not consuming the event, did not work for me. Perhaps a bug 🪲🤔

[Zach Klippenstein (he/him) [MOD]]

I think you’d need to use the Initial input pass to do this, not the default Main. Initial is top-down, Main is bottom-up.

[Pablichjenkov]

Initial and Main first time I heard of it. Could you point out some documentation in regards Zach.
I am consuming Main apparently, because I noticed my events gets passed to the inner most composable.

[Zach Klippenstein (he/him) [MOD]]

https://developer.android.com/reference/kotlin/androidx/compose/ui/input/pointer/PointerEventPass

[Pablichjenkov]

Thanks Zach, I was able to achieve what I want it. Using a combination of

forEachGesture {
    awaitPointerEventScope {
         val eventDown = awaitFirstDown(requireUnconsumed = true)
         ... 
          do {

              val event: PointerEvent = awaitPointerEvent(PointerEventPass.Main)
              ...                      
                                   
          } while (event.changes.any { it.pressed })

ephemient had given me some directions in another thread. I understand the touch API better now. Bellow is a video of what I was describing.

predictive-back.mp4