because i think the default is like "inherit" which means "size to the children"

this is normal behaviour, think of haxeui similar to common web behaviours rather than game dev behaviours and it will make more sense

right

it makes sense when you think about it

oh, i misread your can for "cant" lol

didn't need to explain soz 😂

all good

what do you mean?

so by default, components are autosized, that means they take up the size of their contents (like a buttons size is the size of the label, icon, item renderer and any padding)... you can change this ofc, by just giving it a fixed size (% or px) if you want (or by changing the padding, etc)

note there are some components that come with an "initial size" (eg: textfields and sliders), this is because the contents are either small or non-existent... but, you can always size them as you want

like the mainview.xml?

or each custom component

in each xml file you'd add

<?xml-model href="haxeui.xsd"?>

at the top

I have a bug ! 🙂 . It seems the disabled styling doesn't work anymore for buttons http://haxeui.org/builder/?efkorx When you click on disable, the disable style don't appear.

great.... looks like ive broken something - thanks, ill check it out

is there a way to remove the border of the scroll view? http://haxeui.org/builder/?fitbde

I should probably just use a header

yeah that or an accordian

border-size

, not

borderSize

thx

how do I use

haxe.ui.ComponentBuilder.fromString

nvm got it

hx

@:build(haxe.ui.ComponentBuilder.build("assets/main-view.xml"))
class MainView extends VBox
{
    public function new()
    {
        super();
        appPage.add(new EventPage());
        eventPage.add(new EventPage());
        gatewayPage.add(new GatewayPage());
    }
}

class Page extends VBox {}

@:build(haxe.ui.ComponentBuilder.build("assets/app-page.xml"))
class AppPage extends Page {}

@:build(haxe.ui.ComponentBuilder.build("assets/event-page.xml"))
class EventPage extends Page {}

@:build(haxe.ui.ComponentBuilder.build("assets/gateway-page.xml"))
class GatewayPage extends Page {}

trying to add sub components to a parent component but nothing shows up

tried adding them onReady, tried having the pages directly extend VBox instead of Page

tried addComponent and it seems to hang on an infinite loop. but it freezes when I try to switch to the AppPage tab, not when I instantiate it

So if you are adding components to components you need to use addComponent

you got a minimal repro?

i can share. 1 sec

I should reduce this