Haxe

yeah, not a good way about it at the end of the day

i was thinking having one function to process the click might be a little easier to understand  - especially for folks coming from C++ and java

```haxe
gc_lot.onClick = processClick;
gc_fun.onClick = processClick;
gc_money.onClick = processClick;
gc_opts.onClick = processClick;
```

binding is still useful... just not so much for that use case 🙂

and also, as i mentioned, binding or macros in general, is just helper stuff

tell you what would be nice? Binding by css style name

not going to add it, but that might be nice... food for thought

```haxe
        for (x in findComponents("myMenuStyle", Button)) {
            x.onClick = doIt;
        }
```

its irrelevant - findComponents just builds up a list of children (and children of children to a maxDepth) that match the criterion

`public function findComponents<T:Component>(styleName:String = null, type:Class<T> = null, maxDepth:Int = 5):Array<T>`

i mean, i dont think it really helps any, its a little shorter... but basically, you have, lets say, 5 buttons and they have different functions... its that simple

at some point you are going to need to decide what that function is going to be

yes since each button has it's own function

yeah, so:

```haxe
@bind(...)
function ... {
}

@bind(...)
function ... {
}
```

is _functionally_ equivalent to:

```haxe
@bind(...)
@bind(...)
function ... {
    doSomething(...)
} 

function doSomething(...) {
   ...
}
```

needs to be a haxe resource, not a file resource...