https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • e
    text + named nodes
  • m
    Well I got a couple minor things figured out today, like calculating the absolute position of the component based on its parent. Next up is creating the actual geometry
  • c
    my program segfaulted and i panicked a lot, thinking that there was a bug somewhere in my awful haxe-rust glue code
  • c
    maybe haxe was garbage collecting a rust object or something
  • c
    nope, turns out that TreeView.selectedNode can return null
  • c
    might it perhaps be an idea to add checks for null to some of the methods on TreeViewNode?
  • b
    @ambitious-knife-25690 are your completion times bad? I'm getting 4.5 seconds after including haxeui, alongside ecs
  • b
    i dont understand the question
  • b
    what do you mean?
  • b
    should be able to, you might need to revalidate the component - ill have a play later
  • b
    there is no native counter part to splitter yet
  • b
    how were you building it before?
  • b
    sweeet! 🙂
  • b
    nice, yeah, you backend will be alot more complex i think since you'll need to create your own component tree (events and cliprects can get tricky there), haxeui-kha might help a little for that
  • b
    example app?
  • b
    what does 
    -D module_resoultion_verbose
    output? (be prepared it'll likely be very big - you may want to do it on the command line and pipe it directly to a file)
  • b
    there was a tiny bug with changing node icon dynamically (that i introduced in the last few days), but apart from that - which is fixed now in latest haxeui-hxwidgets - it works as expected:
  • b
    Copy code
    haxe
        setText.onClick = function(_) {
            var s = tv1.selectedNode;
            if (s == null) {
                return;
            }
            s.text = "New Text " + Std.random(0xFF);
        }

        setImage.onClick = function(_) {
            var s = tv1.selectedNode;
            if (s == null) {
                return;
            }
            s.icon = switch(Std.random(4)) {
                case 0: "haxeui-core/styles/shared/error-small.png";
                case 1: "haxeui-core/styles/shared/help-small.png";
                case 2: "haxeui-core/styles/shared/info-small.png";
                case 3: "haxeui-core/styles/shared/warning-small.png"; 
                case _: null;
            }
        }
  • b
    ... ... i get the suspicion you might be using treeview totally differently / wrong - so a code sample might be more useful in the future rather than "modifying the .text, .id, .icon etc of a treeview node doesn't work properly" - since, in my tests, it does, so repro needed really 🙂
  • a
    With kha it was fine
  • b
    i think MSG is is using heaps... iirc i added something to the classpath.excusions and it sped up completion 10x for you
  • a
    with ceramic i haven't really done much work in ceramic to tell, the ceramic project setup is weird and i have standard workflow conflicts that aren't "normal"
  • a
    It did
  • a
    after that point it was great
  • b
  • b
    so would be interesting to see what is the result of verbose module resolution - there is likely some huge dir tree haxeui is iterating through as part of heaps / ecs
  • a
    oh huh, i wonder if local haxelibs make haxeui extra slow...
  • a
    would it traverse a local haxelib directory? 🤔
  • b
    well, it will iterate through everything on the classpath recursively at least once looking for modules (after that it caches things)
  • b
    theres no way around that really, modules could be named anything (folder / haxelib / project wise), and could be anywhere
1...143214331434...1687Latest