> touchable:Bool = true > > Set to false to make this visual (and all of its children) not touchable

but i want it to be touchable? 🤔

no, if you destroy an object you can't use it anymore. If it's a visual, you remove it from its parent and set active = false, then you recycle it. Then when you get a reused object from the pool, you do the opposite

if your text also listens to the pointerOver event, it's parent will be pointerOut-ed when you hover the text inside

I don't understand? I can see this happening, but is there a way around this? or do I need to a custom bounds check on haxeui's side

to say 'children of this parent should ignore pointer events'

or the parent should absorb the pointer events

The deepest child that listens to the event you are testing will consume the event

hmm, i'm confused tho as i apply the pointerevent to only the parent

sorry, maybe i'm missing something really obvious here 😅

I think if you don’t understand how something work, you should create a blank ceramic project to test your very specific use case

And if there is really something not going right on that test case, then you’ll be able to send me that test project so that I take a look

Ah thanks, i'm not sure why i didn't think to try this myself

this works as expected but it doesn't work as expected in the haxeui backend

i figured this is essentially what is going in haxeui when i apply pointer events, but for some reason it isn't 🤔

I am still confused because i'm not sure why what I have isn't working now but i can rule out that I don't understand the ceramic side

There must be something different in the case of haxe-ui, you must simply find what, I guess

interestingly the example loses focus if i overlay the drop down on it

would you expect the dropdown to maintain focus here?

i think the effect above is pretty much what is going on within the dropdown

but i'm not sure what the issue here is 🤔

@billowy-waiter-28954```hx var a = new Quad(); a.depth = 0; a.size(100, 100); a.color = Color.GREEN; var b = new Quad(); b.size(60, 60); b.x = (a.width / 2) - 30; b.y = (a.height / 2) - 30; b.color = Color.RED; a.add(b); a.onPointerOver(a, (info) -> { a.color = Color.BLUE; }); a.onPointerOut(a, (info) -> { a.color = Color.GREEN; }); a.onPointerDown(a, (info) -> { a.color = Color.PURPLE; b.color = Color.PURPLE; }); a.onPointerUp(a, (info) -> { a.color = Color.GREEN; b.color = Color.RED; }); var c = new Quad(); c.depth = 1; c.size(100, 40); c.color = Color.DEEPPINK; c.onPointerOver(c, (info) -> { c.color = Color.YELLOW; }); c.onPointerOut(c, (info) -> { c.color = Color.DEEPPINK; }); c.onPointerDown(c, (info) -> { c.color = Color.LAVENDER; }); c.onPointerUp(c, (info) -> { c.color = Color.DEEPPINK; }); add(c); add(a); ```

okay, this is a repro of what I believe is happening on the haxeui side

even if

c

becomes a child of

a

the pointer events of the parent lose focus

(the above is with

c

being a child of

a

)

This is normal behaviour. c is listening to pointerOver/Out, so it takes priority over its parent, thus the parent loses focus when the child a gets it

how would I work around this? In the actual backend c never assigns pointer events

so it seems odd to have it steal focus

I don't know what you are doing exactly with haxe-ui, but this is the same behaviour as, say, html5