i would always have to be the bottom most child though

as other components would be added on top of it

but there is likely functions to handle all that

what is the bottommost child?

well, i mean, say you have a vbox with a background image, that would, presumably be a Graphics added to the vbox Object

well, that vbox would also have buttons added to it (more Object's) but the background graphics Object would always need to be child index = 0

ok got it

i dont think that would be a problem, i mean, i dont KNOW that heaps has a setChildIndex, but im going to assume it probably does

so i guess the componentimp could have an array of Graphics objects, that will always be at least .length = 1 (for "normal" styles), if a different background image + image clip + image slice is detected then it makes a new one

in fact, maybe a map makes more sense and the key being the image+clip+slice

I used a container at index 0 that holds all the style Graphics

but the problem is that the "extra" object now seems to ruin the haxeui's hierachy

is there a way to tell haxeui there is always one base object so that stuff like

numComponents

should ignore that when counting?

num components should only report the number of components added via addComponent

It is a simple change and it is working (button hoverable) but the buttons in the background are gone

hmmmm... thats weird... its not an alpha issue is it?

nope

I have to check why...

right, fair enough, certainly seems strange, i mean, that yellow background is just another "overlay" component added to the Screen

so why that would remove the ones behind seems weird... especially as the dialog in the front seems fine (and thats pretty layered itself)

Current doing this: add a base style container in ComponentImpl then add Graphics to it in StyleHelper

.removeChildren maybe?

but the container only contains styles Graphics (supposed)

oh you mean haxeui maybe adding components to that index-0 container too?

possibly, yeah, i mean, you are removing all the children from the component

ah, no you arent

so i guess i would verify that the first child (index 0) is what you expect it to be, its possible that haxeui is adding a child at a specific index

oh actually there are components:

../haxeui-heaps/haxe/ui/backend/heaps/StyleHelper.hx:16: h2d.Object
../haxeui-heaps/haxe/ui/backend/heaps/StyleHelper.hx:16: h2d.Interactive
../haxeui-heaps/haxe/ui/backend/heaps/StyleHelper.hx:16: haxe.ui.components.Label
../haxeui-heaps/haxe/ui/backend/heaps/StyleHelper.hx:16: haxe.ui.components.Button
../haxeui-heaps/haxe/ui/backend/heaps/StyleHelper.hx:16: haxe.ui.components.Label
../haxeui-heaps/haxe/ui/backend/heaps/StyleHelper.hx:16: haxe.ui.components.Button
../haxeui-heaps/haxe/ui/backend/heaps/StyleHelper.hx:16: h2d.Object
../haxeui-heaps/haxe/ui/backend/heaps/StyleHelper.hx:16: h2d.Graphics
../haxeui-heaps/haxe/ui/backend/heaps/StyleHelper.hx:16: h2d.Graphics
../haxeui-heaps/haxe/ui/backend/heaps/StyleHelper.hx:16: h2d.Graphics

oh yeah, interactive is a must too, other wise you dont get events

so i guess you need to always make sure the first child is the container