https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • a
    that was my next question heh
  • r
    Oh wow, that was fast. I'll try it out, thanks!
  • b
    cool - let me know if you have issues... CI passes so i think its all fine
  • a
    it fails on the removal of the last added component
  • a
    it leaves a "part" of the full component behind
  • a
    like it will remove the text but leave the bg
  • b
    ¯\_(ツ)_/¯
  • a
    oh, hmm....
  • b
    Visuals are sorted by depth, so the order in 
    children
    shouldn't matter. Why would you need to do that?
  • b
    is the depth order "per parent"? I mean, this for example:
  • b
    Copy code
    A (depth = 1)
    B (depth = 1)
    C (depth = 2)
        X (depth = 1)
        Y (depth = 2)
        Z (depth = 3)
    D (depth = 3)
  • b
    are those depths sensible? Or would it be 1, 2, 3, 4, 5, 6, 7, etc
  • b
    Yes it's per parent by default (although that can be changed with the 
    depthRange
    property)
  • b
    great, so yeah, its all as discussed then NotBilly
  • b
    Jeremy: for your understanding, in haxeui, the position of the child in the children array is effectively its zorder
  • b
    Yes, that's fine, as long as it is translated correctly into depth values for Ceramic (which is fairly easy to do, like in the code you shared above)
  • b
    yeah, its all pretty trivial, just need to align the depth with the index... no biggie... just wasnt sure how far you had scrolled 🙂
  • a
    I've got the indexes aligned but I'm having a weird issue where only the first added button is improperly being removed
  • b
    is the GH code up to date?
  • a
    2 secs i can push
  • a
    @bright-gpu-74537
  • b
    i dont quite get this impl: https://github.com/Jarrio/haxeui-ceramic/blob/master/haxe/ui/backend/ComponentImpl.hx#L205-L226 Why not just do:
    Copy code
    haxe
private override function handleRemoveComponentAt(index:Int, dispose:Bool = true):Component {
    return this.handleRemoveComponent(this.childComponents[index], dispose);
}
  • b
    you can also replace: https://github.com/Jarrio/haxeui-ceramic/blob/master/haxe/ui/backend/ComponentImpl.hx#L181-L191 with:
    Copy code
    haxe
private override function handleAddComponentAt(child:Component, index:Int):Component {
    return this.handleAddComponent(child);
}
    Since you dont really care about the index (depth), you'll assign them later in mapChildren
  • a
    huh, that is way smarter
  • a
    yep, looks like it was my bad code that caused the issue
  • a
    over engineered 😅
  • b
    🙂 so that works now? How does your "everything is fucked" test case look now?
  • a
    this is the first time i've seen notifications properly overlap that line
  • b
    🥳 So menus will also work now... as i suspected, the issue was your "layering" of components
  • a
    i still can't select an item on a list view
1...157115721573...1687Latest