Haxe

When  you select the second optionbox, it doesn't get bold,

`<vbox>
    <style>
.bold .label {
    font-bold: true;
}
</style>
    <optionbox text="I am born bold" styleNames="bold" />
    <optionbox text="Check Me to add boldness!" onchange="this.text='should be'; this.addClass('bold');" />
    <optionbox text="Check Me to add boldness!" onchange="this.text='should be b'; this.addClass('bold');" />
    <button text="Click Me!" onclick="this.addClass('bold');" />
</vbox>`

the option box with the text "should be" doesn't work, the option box with the text 'should be b' works,

shouldnt <optionbox> be in a <dropdown> not directly in <vbox>?

Interestingly this works
http://haxeui.org/builder/?qoulsq
this doesnt
http://haxeui.org/builder/?zktahz
also clicking items in order 2,3 or 3,2 has same wrong effect
http://haxeui.org/builder/?ezccim adding class without changing text never works

that does feel like a bug - so basically, just to understand the selected option box should be bold, right?

hang on, dont you also need to remove bold?

oh, but yeah, it still doesnt work as i would have expected it

is it possible to only add certain components in xml markup depending on whether a compiler flag is set?

So for example a component is ignored if a `dev` flag isn't set

hmmm, i try to avoid this type of "logic in xml", but you might be able to get away with it

i _think_ there is a condition attribute, but i dont know how deeps it goes, i know its available for modules

so... there is defo is a condition attribute, im just trying to remember how it works

... right, so "condition" seems a little broken, i guess, i should fix that, however, you can use "if" or "unless" and that seems to work, eg:

without `-Dsomeprop` the "Bob" button wont show

yh, tbh I'm usually like that as well 😅 is there another way you'd recommend instead of that? I can hide the components but i would prefer if they didn't end up in the generated code

honestly, i would (and do) prefer an #ifdef

the if / unless is there for you to abuse, im not a fan, but im sure there are use cases

yh, hm, I guess I can just remove their logic on the code side, that's probably the main thing

just, to me, the idea of `<include source="debug_window" if="debug" />` seems totally sensible at the time, but its (again, to me) awful design