Haxe

ok, then no, you probably dont need to use ready event, still strange that the behviour is different between hxcpp and neko, so ill still check it out

I'm still curious what exactly onReady is supposed to be used for? what it tells us?

honestly, its mainly used internally, it essentially means "component is done initialising, its added to "stage" (for openfl), and its had at least one invalidation"

oh I see. that was the first thing I assumed )

yeah, your assumption was correct, but _generally_ you dont need to use it

oh I think I found the problem though still not sure why it happens... I used a local var for storing result of buildComponent and everything start working even the onClick event, even for neko target.

at first I used class property ui:Dynamic to store the built component

what if you used a class prop ui:Component ?

I was not sure what type to use to store because docs does not mention ))

out of interest, does "ui:Any" also work?

i mean did not compiled when i tried to access ui.joinButton

actually all my code is working now as I wanted in my first question here.

ok, great... so, note to self: dont use Dynamic for the UI as a result of buildComponent

looks like Dynamic is driving your macros crazy )

i think its because the macro returns `Expr`

yeah I read the code of buildComponent so I was not sure what to do with Expr ))

```haxe
    macro public static function buildComponent(filePath:String, params:Expr = null):Expr {
        var builder = new CodeBuilder();
        buildComponentFromFile(builder, filePath, null, MacroHelpers.exprToMap(params), "rootComponent");
        builder.add(macro rootComponent);
        return builder.expr;
    }
```