Like the player dying

im just heading off, but you'll have to knock up a sample of what you mean... im guessing you can do it in xml, but you can certainly do it in "normal" haxe

Alright... Say I have this template:

<label ttext="alive"></label>

how do I change the text from the Player class when the player dies.

im not 100% sure im following, but if i am, i would give it an id and use something like

myPlayerUI.aliveLabel.text = ...

how are you building this "" UI?

That works... I was hoping that a better way existed thanks for taking the time to clear things up 🙂

if you are using the @:build macro you can use binding

but i dont know if you are or not

... ill knock up an example real quick anyway... two secs

Thanks for pointing that out.. I'll explore the code for that macro and see if its what I want

:>

the "interesting" part here being:

@:xml('
    <vbox>
        <switch id="playerAliveSwitch" />
    </vbox>
')
class MyPlayerUI extends VBox {
    @:bind(playerAliveSwitch.value) public var isAlive:Bool;
}

ie, "isAlive" is bound to "playerAliveSwitch.value", so you can just access it externally as if you were doing "player1.playerAliveSwitch.value"

(again, not totally sure if thats what you are asking for 🙂 )

i think they might want something like

<label value="Whatever.alive" ifTrue="alive" ifFalse="dead">

and then it automatically changes the text based on the value of

Whatever.alive

which doesnt seem like something haxeui would do itself, but that effect is certainly possible

yeah, you would need some kind of way that links the two parts

i'm working on this myself, my immediate thought is event system (I'm using an ecs base)

haven't gotten to mixing the ui and composite, just yet, but i've been idly thinking about it as i build up my framework base

at least, i think an event system would have the "easiest" use, but I may think otherwise when i actually start working on that stuff

you can write functions in blocks in XML and call them from onchange attrs if you want and that can make component states rely on one another - but you can also do it from Haxe - but they suit different use cases

I got a compilation error due to incorrect assignment in a function in a script which is in itself fine. But the error was hard to track down because of where it was flagged. It was in completely the wrong place. In ui.xml I have this in a function:

// Scene
                            rubiks = true;

Now rubiks is an optionbox and I meant to assign rubiks.selected = true. In my UI.hx file the error was reported several lines away from the field which was binding to this field:

@:bind(diffuse.value)         <-------------------error flagged here
    public var diffuseColor(default, null):Color;

    @:bind(specular.value)
    public var specularColor(default, null):Color;

    @:bind(shininess.pos)
    public var specularShininess(default, null):Float = 5;

    // Scene properties
    @:bind(rubiks.selected)
    public var sceneRubiks(default, null):Bool;   <----- Bool bound here

error: Source/UI.hx:56: characters 3-16 : Bool should be haxe.ui.components.OptionBox

so the error was correct but it was on the wrong line.

ill check it out...

I updated HaxeUI (and Flixel) for the first time in a while, and it looks like this has regressed, and the example does not work for me anymore https://discord.com/channels/162395145352904705/565569107701923852/1022798863909785640

hmmmm, weird... can you knock up a sample? Or post your app? Ill check it out at some point later

oh cool. It is actually the same zip from the post above the one I linked https://discord.com/channels/162395145352904705/565569107701923852/1022795956565061632 That should work correctly, but then if you start the

contentArea

as hidden, by setting hidden to true in the

main-view.xml

, then it doesn't toggle with the button anymore

That would absolutely kill haxeui for games though

at least, full electron can't be embedded because of Javascript not being allowed (JIT forbidden) on some targets.