https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    well, its fully functional, but just not how i want a real treeview work in core when i get round to it
  • b
    (the real one i want to use itemrenderers and data sources, this is just a bunch of expandable and collapsable boxes in a scrollview that must be manually populate via code)
  • b
    so its less than idea
  • b
    gimme a few mins to extract it and test it
  • f
    Great 🙂 Don't rush, I'm about to go off and wash the dishes 😄
  • b
    👍
  • b
    i also added the splitter components from the same project as you might find them useful too
  • b
    Copy code
    xml
    <hbox>
        <treeview id="tv" width="200" height="300" />
        <splitter direction="vertical" width="400" height="400" style="border:1px solid #eeeeee">
            <box width="100%" height="70%" style="background-color: #FFCCCC;" />
            <splitter width="100%" height="30%" style="background-color: #CCFFCC;">
                <box width="20%" height="100%" style="background-color: #CCFFFF;" />
                <box width="50%" height="100%" style="background-color: #FFFFCC;" />
                <box width="30%" height="100%" style="background-color: #FFCCFF;" />
            </splitter>
        </splitter>
    </hbox>
  • b
    the treeview you will have to populate in code
  • b
    Copy code
    haxe
            var tv:TreeView = mainView.findComponent("tv");
            var root1 = tv.addNode("Root A", "icons/folder.png");
            root1.expand();
                var parent1 = root1.addNode("Parent 1A", "icons/folder.png");
                parent1.expand();
                    parent1.addNode("Child 1A-1", "icons/page_white.png");
  • f
    Woah! Early Christmas! Awesome, thanks for sharing. The tree should be perfect for layers, too 😄
  • f
    Haven't got the splitters in yet, but the tree is pretty cool! Because assets are referred to by path, assets with spaces in their name are broken. It might be interesting if the names of files weren't shown (file names 1...13 hardly add value, and seem like they'd be common amongst assets). Maybe all files in a folder could be shown together as a grid of squares, like krita does. Anyhow, screenshot 😄
  • f
    Krita shows brushes in a grid
  • b
    looks goods 🙂
  • b
    i think im going to put the splitters into core
  • b
    jesus, HD likes child processes
  • p
    I'm pretty sure vscode also likes those.
  • b
    ... i wonder what its using neko for
  • b
    lime project?
  • b
    lime CLI tools are neko
  • b
    technically haxelib.exe is just a renamed neko.exe with some neko bytecode too, I think
  • b
    gotcha, yeah, openfl
  • b
    didnt know that about haxelib being compiled to neko bytecode, but now you say it obviously makes total sense
  • b
    HaxeDevelop has also had some issues with leaking processes during completion / not properly closing them
  • b
    but I thought those were fixed
  • b
    macros spawning processes can also cause that
  • b
    flixel has a build macro that invokes haxelib to, and for a while there was no process.close() call..
  • b
    i think the HD process leak is defo still there, ive had like 20 haxe.exes running before after HD has closed...
  • b
    not recently though, but defo seen it happen
  • b
    I think HD doesn't keep one Haxe server process running constantly like vshaxe
1...313314315...1687Latest