Haxe

I don't know how I can toggle another element's `hidden` attribute from scripting in haxeui xml

```xml
<vbox style="padding: 5px;">
    <box id="container" style="padding:10px;background-color: #FFCCCC;">
        <button text="Contents" />
    </box>    
    <button text="Show / Hide" onclick="container.hidden = !container.hidden;" />
</vbox>
```

... I was using `onClick` instead of `onclick` x)

🙂 i might fix that actually, ive done that before, i might make it so oNcLiCk would still work

Ok can't seem to reproduce without coconut

Any idea what I should invalidate to properly apply `hidden` changes?(to children)

I added `if (prop == "hidden") target.invalidateComponentDisplay(true);`, which works.. but not the first time 😆

i would have thought that hidding the parent should have been enough

i mean, in haxeui im pretty sure im not iterating through all children and hiding them explicitly - hiding the container should be fine (for all backends)

so looking at haxeui-core, it looks like hidden is just passed off to the backend (handleVisibility)

```haxe
    public function hide() {
        if (_compositeBuilder != null) {
            var v = _compositeBuilder.hide();
            if (v == true) {
                return;
            }
        }

        if (_hidden == false) {
            _hidden = true;
            handleVisibility(false);
            if (parentComponent != null) {
                parentComponent.invalidateComponentLayout();
            }

            dispatchRecursively(new UIEvent(UIEvent.HIDDEN));
        }
    }

```

```haxe
    private function set_hidden(value:Bool):Bool {
        if (value == _hidden) {
            return value;
        }
        if (value == true) {
            hide();
        } else {
            show();
        }
        return value;
    }
```

Hmm `show()` is called and takes the whole path (_hidden == true and parentComponent != null)

hidden=true supposedly works since everything disappears correctly

ok, so that make sense... wonder why its not actually working then

is maybe coconut hiding all children? I mean, i guess it goes through all children and sets properties?

so maybe its hiding the container and all its children explicitly (though then i would have assumed the same would happen with show)

It doesn't know enough to propagate some attributes to children

ok, thats a good thing i think, right? In this case you dont want it to

i wonder if handleVisibility is being weird for some reason

Another element: it only happens to children that have never been updated

i would have thought handleVisibility is quite simple