Morning folks, is there any way to detect clicks further up the compose tree? I have a child that toggles visibility of a local element, but I want the clicks on the root to cancel (basically a pop up box that when you click outside of the popup it will close it)

I don't think using ambient will be the right approach here. If you want parent to be able to control state of the child, why are you hesitating to bubble up this state? e.g.

@Composable fun RootComponent() {
    var popupOpen by state { false }
    Clickable(onClick = { popupOpen = fasel } ) {
    SomeLayoutToPositionSomewhere() {
        DropDownItem(open = popupOpen, onPopupOpen = { popupOpen = true })
    }

Doesn't look that scary, does it? 🙂

Ok, really hesitating because it depends how far down the tree the popup is and how to make it scalable say if you have X number of popups

With ambients, this very explicit state becomes implicit, which will easily lead to complicating when project/screen will grow or when you start to refactor something.

cool yeh sounds like ambients is not the right solution though passing down state from up above depends on how far that drop down is

Re scalability:

DropDownItem(open = popupOpen, onPopupOpen = { popupOpen = true })

I think this gives you a lot of flexibility and scalability, TBH. It's stateless, so you can put it on any screen, with any architecture and its parameter set clearly indicated expectations from the callee

yeh maybe I am missing something but if

SomeLayoutToPositionSomewhere() {
        DropDownItem(open = popupOpen, onPopupOpen = { popupOpen = true })

was somewhere else in another file>? would need to pass

popupOpen

as an argument

True, because it becomes the contract of this composable as well

cool, and if I had more than one popup then I would need ot declare state

popupOpen1

popupOpen2

etc?

More than one popup on the screen? Yes, it seems like you want to have state for every popup, or you can create one state to hold everything, e.g.

data class ScreenState(val popup1Open: Boolean, val popup2Open: Boolean)

and copy and propogate new state every time

yeh that could work nicely 🙂 maybe that would be the best approach

No problem 🙂