Haxe

well, put simply, the depth should reflect the position it is in the childComponents array

tbh, i could just make depth == childComponents.length 🤔

well, no... because then you are basically saying "always put this and the end" (depth wise)... you'll need to _reassign_ depth based on array index

but haxeui may reconfigure the childComponents array, no?

only via add/remove component, it wont do it internally by screwing with the array

if it did, all backends would act all strange

basically the childComponents array is the "gold standard" for the order of the children, which for ceramic also indicates its depth

so essentially if i sort out the addcomponentat I can deduce the remove from the index

well, its not really about addcomponent, addcomponentat, removecomponent or removecomponentat... its: when you add or remove a component (handleAddComponent, handleAddComponentAt, handleRemoveComponent, handleRemoveComponentAt) you will need to reorder the depths in order to refect the new state of things... same goes for addComponent / removeComponent on Screen.instance

is there a place where I can flag a state update?

these guys seem to be one step before actually updating the core list, so i need to update the list after the return of these - no?

hmm, i guess not because i know what has changed before i return lol

no: https://github.com/haxeui/haxeui-core/blob/master/haxe/ui/core/Component.hx#L401-L403

```haxe
function handleAddComponent {
    // do stuff
    reasignDepths();
}

function handleAddComponentAt {
    // do stuff
    reasignDepths();
}

function handleRemoveComponent {
    // do stuff
    reasignDepths();
}

function handleRemoveComponentAt {
    // do stuff
    reasignDepths();
}

function reasignDepths {
    var n = 0;
    for (c in this.childComponents) {
        c.visual.depth = n;
        n++;
    }
}
```

it doesnt matter 😄

Its about the depths being wrong...

hmm, maybe this means i'll have to have a root passed to toolkit

I guess that's fine, now that I understand ceramic a bit better that isn't a big deal

thinking in reverse again, i'm still following ceramic hierarchy - not haxeui's

its not a bad idea to have that as an option anyway, but in this case, it doest mean anything... the version in screen is exactly the same as the psudo above, just instead of "childComponents" you would use "rootComponents"