https://linen.dev logo
Powered by
# haxe-ui
  • b
    how to specify the minimum width of the box when using a splitter? - when I try to set the min-width (commented in the code below) the program falls into infine loop (tested on Heaps and the builder)
    Copy code
    xml
<vbox width="100%" height="100%">
    <style>
        #hierarchy {
            width: 100%;
            height: 100%;
            /* min-width: 30px; */
            background-color: red;
        }

        #workspace {
            width: 100%;
            height: 100%;
            background-color: green;
        }
    </style>

    <splitter width="100%" height="100%">
        <box id="hierarchy" />
        <box id="workspace" />
    </splitter>

</vbox>
  • b
    @bright-gpu-74537
  • b
    @bright-gpu-74537 Why does the 
    addCustomNode()
    function add empty fields? In my opinion this should be equal to the 
    addDefaultNode()
    function, but it is not
    Copy code
    xml
<vbox width="100%" height="100%">
    <script>
        function addDefaultNode() {
            hierarchy.addNode({text: "10", icon: "haxeui-core/styles/default/haxeui_small.png"});
        }

        function addCustomNode() {
            hierarchy.addNode({picture: "haxeui-core/styles/default/haxeui_small.png", count: "10"});
        }
    </script>

    <tree-view id="hierarchy" width="300px" height="100%">
        <item-renderer id="expandable" layoutName="horizontal" width="100%">
            <image id="picture" verticalAlign="center" width="40px" height="40px" />
            <label id="count" verticalAlign="center" style="color:#888888;font-size: 11px;" />
        </item-renderer>
    </tree-view>

    <button text="Add default node" onClick="addDefaultNode()"/>
    <button text="Add custom node" onClick="addCustomNode()"/>
</vbox>
  • b
    im insanely busy atm (juggling multiple projects and context switching all the time), so wont have to time to look at this (at the very least) until the weekend. > how to specify the minimum width of the box when using a splitter there is a bug in splitter that leads to an infinite loop, and also a bug in min-width - they've been on my radar for a while > Why does the.................. the code looks sensible - i would expect the same results, the treeview is still experimental - though tbh, im surprised the item renderer part didnt work - ill have to check it out
  • h
    ok - I got a test app built - just the equation table. I've noticed a couple of things. 1. If the error text wraps in the column the first time it's displayed it's ok. The second time it only shows the first line - half the error text is not visible. 2. I cannot figure out how to get placeholder text that is specific to the column given there is only one renderer class. 3. As the rows expand down the page because of the error display, even though a scroll bar appears, the table expands and overlaps the other elements. This is despite the fact that it has a fixed height. 4. If I use a datasource class it has to have a field for the theValue field. This isn't strictly necessary as the onValue() function copies the values to the right field. I don't know if an enhancement to make non-backed fields possible would be useful but it's not a huge deal to add another field to the row class. But I have what I think is a workable understanding of the way to use a dataSource class. I'll prep a repo with this test project in it in case it's helpful to you to see the code.
  • h
    @bright-gpu-74537 The code is in I realize you are busy. I can make progress I think based on what I have so far, but would be interested in any feedback when you have time.
  • b
    cool - will take a look over the weekend 👍
  • i
    possibly a haxeui-flixel bug: when I open a custom dialogue box, it works fine, but if I then try to create a new instance of the same custom dialogue box again, the app segfaults if the previous box was closed using one of the buttons (i.e. OK, Cancel), but not if it used the [X] in the right hand corner
  • i
    I have custom dialogues for my world saving and loading, which makes it a bit annoying that I can either only save or only load once
  • i
    on better news: steam deck with bigger font size makes haxeUI feel VERY adaptable!
  • h
    Is it not valid to add the invalid-value class to just any textfield ? I tried it on one not in a renderer and it popped up the in-game debugger ?
  • b
    i think there is a property if you want to reuse dialogs... ill fish it out
  • b
    myDialog.destroyOnClose = false
  • b
    it should be, im pretty sure i added "invalid-value" class to the theme the other day
  • i
    does closing a dialogue with either button not destroy it after calling the handlers it has?
  • b
    yeah, i might have read your issue wrong (just woke up - not enough ☕ )... i think you are creating a new instance each time anyway, right?
  • i
    yeah
  • i
    and same lol
  • b
    OK, so yeah, if you are creating a new instance of your dialog class, then you arent trying to reuse it, so ignore the above, does sound like a bug... any chance from a minimal repro?
  • i
    will do
  • b
    thanks, much appreciated 🙂
  • b
    this seems to work fine: http://haxeui.org/builder/?sqwtfk
  • b
    OK, so i made an example for you, and some comments: http://haxeui.org/builder/?rebulc
  • i
    hmm I can't reproduce in a new project, time to see if it's my own stupid code
  • b
    also @blue-lock-94355 - i think im going to add new property to item renderers, something like "type" or "for", so its not reliant on "id" as thats a little esoteric and i can certainly see how there was some confusion there. So i think its better to have something like:
    Copy code
    xml
<item-renderer for="expandableNode">
...
...
...
  • b
    dropdowns have a similar thing where you can have two item rendererers, one for the list and one for the actual button - normally they would use the same one, but if you specify an id of "dropdownRenderer" then you can use a different one for the button, which is a nice feature, but again, a little esoteric... i think a 
    <item-renderer for="button">
    is alot clearer. (?)
  • b
    (just need to think of a decent, clear and not-so-ambiguous name)
  • i
    ok, my issue seems to be to do with FlxCameras being assigned to Dialogs and haxeUI not being able to find them
  • b
    :/ ...flixel cameras... :/
  • i
    happens in this function in StateHelper.hx:
    Copy code
    hx
 public static function findCameras(member:FlxBasic, group:FlxTypedGroup<FlxBasic> = null):Array<FlxCamera> {
        if (group == null) {
            group = currentState;
        }
        
        if (group == null || group.members == null) {
            return null;
        }
        
        for (m in group.members) {
            if (m.cameras != null && m.cameras.length > 0) { // <----- this line
                if (m == member || ((m is FlxTypedGroup) && hasMember(member, cast m))) {
                    return m.cameras;
                }
            }
        }
        
        return null;
    }
    Null Object Reference
1...115811591160...1687Latest