although, just looking at heaps there is a syncPos function that i think might do what im after anyway

@User if I use a custom component can I get rid of all the findComponents I need to use in code? Maybe using binding?

yup... 100%... its the main point in using custom components + xml

ah ok.... it was getting a bit unwieldly

everything with an id becomes a typed member var automatically

got it

finally got a layout working that I can animate for the Heads Up display

> it was getting a bit unwieldly i find that any UI of size becomes a management nightmare without xml personally (haxeui or not)

the xml is pretty good - it was the Haxe code starting to get out of hand since I need to touch almost every one of the 19 elements so far

sure, same applies i guess for using the UI... you can write a bunch of findComponents in the constructor i guess

but easier to let haxeui handle all that stuff for you (i think)

that's what was getting out of hand - custom component will make it a lot nicer

100%

ok - let me scratch my head about that. I got your guide up looking at the binding part

first part is easy as:

whack:

@:build(haxe.ui.macros.ComponentMacros.build("myxml.xml"))

at the top of a class

thats kinda it now... if your xml had a

<button id="bob" />

in it... then you have a

var bob:Button

as a member of that class now

you can also then use binding too:

haxe
@:bind(bob.text)
var bobText:String;
@:bind(bob, MouseEvent.CLICK)
function onBob(e) {
}

I set this

class Hud extends Component

as the class since the xml is a mix of box/hbox/vbox/absolute

whats the root of the xml though? Thats this class essentially

vbox

then

class Hud extends VBox

is more correct

kool

Cool ,thanks

@User if I use @:build to make the Component, how would I access that component from another Class to do something like show() or hide()?

There's no code for handling touches, only mousepointer

> There's no code for handling touches, only mousepointer gotcha > how would I access that component from another Class Im not sure i follow... there is no difference between a custom component / view and a, say, button... unless you mean you want access it from xml, in which case you'll need an entry in your module.xml

> Its important to mention module.xml here and the role it plays in exposing HaxeUI component classes to the markup parser (eg: xml). If you are using HaxeUI solely through code (ie, creating instances of components in haxe code manually) then module.xml need play no part. However, if you plan to use any of the markup parsing features (ie, creating instances of components and layouts in xml) then you need to be aware that these are exposed to HaxeUI via a module.xml. There are various ways to do this depending on the way that you are creating custom components but the general principle is that you create a module.xml file somewhere on your class path and let HaxeUI know about your custom components