what did it look like (i mean the xml) before when it didnt work with widths/heights

width at 100%

on a vbox set at percentWidth = 16

yeah, exactly, if you are making a custom composite component out of existing components, then you dont really need behaviors because they are all set up for you in haxeui-core

getter/setter working too!

🙂

not sure if you are using a module.xml but you can also expose that to haxeui so you can use it in xml also

yes, module.xml

is working

ok, so it was the height=100% with bugged it

but I don't know why

.error { font-size: 14px; color: red; font-style: italic; } .hint { font-size: 14px; font-style: italic; }

this doesn't work

remove the height="100%" and everything will be fine

ok, so when you use @:build it creates a wrapper component around your custom component

eg:

yes it's why I have @:build(haxe.ui.macros.ComponentMacros.build("assets/ui/moduletextfield.xml")) class ModuleTextField extends VBox { public var tfText(get, set):String; private function get_tfText():String { return hint.text; } private function set_tfText(value:String):String { hint.text = value; return value; } public function new() { super(); percentWidth=16; } }

this is "essentially" like having:

but without height anywhere, it seems it's lost

so when you use % heights, you are "essentially" saying:

in which case haxeui is like "100%" of what??

so

yes, it's the talk we already had

I find it strange...

it's not 0

but what it is..?