https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    yeah, something is off... i would review and sanity check all the "add/remove child" code
  • b
    whether its depth or X or Y
  • b
    (i just had to google how to spell "whether" 😄 - wheather? weather? whether? ffs)
  • a
    lol
  • a
    @bright-gpu-74537Does removeAt, only ever remove the first component in the list? 🤔
  • b
    no, it removes the child at the specified index
  • a
    this is problematic
  • a
    @billowy-waiter-28954 is there a way to remove/insert children at specific index's?
  • a
    the api makes this very >> not okay <<
  • b
    is it all depth based?
  • a
    it is
  • a
    and an index won't be "unique"
  • b
    does it also take aprent child into account? I mean, say this tree and depth, will that "work":
  • a
  • a
    I think it could
  • a
    but i'm not sure on how this works
  • b
    Copy code
    A (depth = 1)
    B (depth = 1)
    C (depth = 2)
        X (depth = 1)
        Y (depth = 2)
        Z (depth = 3)
    D (depth = 3)
  • a
    that's the default behaviour, yeah
  • a
    except depth doesn't auto increment
  • b
    ok, so, why dont you get the child components, and assign them the depth based on the position in the 
    childComponents
    array, eg:
  • a
    I did mess with that, but, I didn't think about matching it with the childComponents array 😄
  • b
    Copy code
    haxe
var n = 0;
for (c in this.childComponents) {
    c.visual.depth = n;
    n++;
}
  • b
    (not tested, just written blind)
  • a
    Copy code
    hx
    function getDepthIndex(child:Component) {
        var depth = 0.;
        var children = child.visual.children;
        if (children != null && children.length > 0) {
            depth = children[children.length - 1].depth;
        }
        return cdepth++;
    }
  • a
    that's somewhat what i'm doing now
  • a
    but i was basing it off of ceramic's children 😅
  • b
    but the ceramic children might be wrong, no? I mean index wise... also, you are taking the last one and incrementing the depth, not assigning it a fixed value based on array index
  • b
    ... so that bit of code is almost certainly the source of your woes
  • a
    yeah, i removed most of it and have quite a simple new base that mimics my best version
  • a
    at one point it did make a difference, but now it goes away 😄
1...156915701571...1687Latest