try adding `-D ABI=-MD`

well that solves that, except the app now just shows a blank window

https://plzlookat.mystupid.pictures/uIQbNnfRpm.png

and something is defo supposed to show? You have pulled latest for all haxeui libs (and hxWidgets)?

the fact its created a window means its working

yeah it shows up on HTML5 build

I'll make a GH repo for it a sec

same

thats a good thing 🙂

two ready's

oh god how did that happen

¯\_(ツ)_/¯

and how did HTML5 build work anyway <:thonk:533013422204256276>

html5 app.ready is super uninvolved, so it likely just calls the callback right away

<@385014891750096896> there's a bug with TreeView class that still hasn't been fixed https://github.com/haxeui/haxeui-flixel/issues/29

nice, thanks for the warning

ill make one

Hi, Ian. I'am trying to implement my own GUI library and I faced with a problem, so I want to ask you for advice How do you handle layouts? I split my code to tree traversal multiple times, at the first I calculate the width and the height, at second I calculate positions. There are not to many ways to handle a tree, so I suppose you did something like this solution too. How do you handle size calculations in layouts? - their sizes may be a) absolute (there are not need to special handling), b) relative to children (so you need to calculate children sizes first), c) relative to parent (so you need to calculate parent size first). How do you handle b) and c)? In my library I traversal from child to parent with `depth-first LRN` algorithm, for the current component it records their absolute size to `State` if it has an absolute size (usually regular components with known size such as `text`, `button`, ...) or if it is a layout and size of the children already calculated. Then layouts (row, col, ...) (still for the current component) calculates and records children size relative to it (if child specify that their size is relative to parent). For c) there are no special case, because at the moment it will be already calculated at the previous step So I illustrate a problem at the two examples below In my library the first example calculated without problem, but algorithm broke for the second case, because size of the nested component (with styleNames="test3") calculated in the nested component (with styleNames="test2") but their size is unknown - its size will be calculated in outer component (with styleNames="test1"). So how do you travel through the tree to avoid this problem? Do you recalculate tree and propagate sizes to a children in multiple steps after you see relative to parent size or you do it something else?

```html <vbox style="padding:15px;width:100%;height:100%;spacing:20px;"> <style> * { border: 0px solid black; padding: 0; } .test1 { background-color: green; } .test2 { background-color: yellow; } .test3 { background-color: purple; } </style> <!-- example 1 --> <box styleNames="test1" width="100px" height="100px" > <box styleNames="test2" width="60%"> <box styleNames="test3" width="30px" height="30px" /> </box> </box> <!-- example 2 --> <box styleNames="test1" width="100px" height="100px" > <box styleNames="test2" width="50%" height="50%"> <box styleNames="test3" width="90%" height="90%" /> </box> </box> </vbox> ```

actually, in your second example is that even needed? test1 would be 100x100, test2 is easily calculated as 50x50, and that means that test3 is easily calculated also as 45x45

in haxeui once you set test2 to 50x50, it wll also invalidate its parent, which in this case (i think) means it will skip it since its already being validatd

how do you implement this `before`?

<@385014891750096896> https://www.newgrounds.com/dump/download/3168b4b259834b65ce0b9f7f07956769 also uploaded the source to newgrounds dump because discord's 8mb lol

okay, I think I understood, thanks!

yeah, same 🙂

nice

also thanks