(its disabled not allowInteraction)

I'm getting haxe/ui/binding/BindingManager.hx:212: EInvalidAccess(itemCount)

When trying to make disabled="${animationList.itemCount == 0}"

is item count a public property of listview?

not sure it is...

animationList.dataSource.size

might be what you are after

haxe/ui/binding/BindingManager.hx:212: EInvalidAccess(dataSource)

hmmmm, thats weird

weird it works here: http://haxeui.org/builder/?utdebw

Should this change in your example work? 0}" />

yeah, something is strange there: http://haxeui.org/builder/?useyjg

EInvalidAccess(dataSource)

locally

😉

now just to understand why

even more strangeness:

<button text="Test" onclick="trace(lv1.dataSource.size);trace(lv1.dataSource.size > 0)" />

works fine... :/

I feel like I'm developing some kind of sixth sense to discover odd stuff in haxe ui 😆

heh heh, not a bad sixth sense to have... ill take it if you dont want it! 😄

Does anyone know with Flixel how to avoid Haxe UI disappearing on state change?

i guess you would have to add it to the state again? I mean, im certainly no expert in flixel, but regardless of haxeui how would persist an object between states?

That's what I'd do

Which means recalling Toolkit.init I suppose... will give that a go

no no, you shouldnt need to reinit toolkit... i mean, you can, it should have no effect, but i would just init toolkit in your entry point (Main.hx or whatever)

ive actually thought about doing away with toolkit.init entirely - just having it "auto init"... it seems feasible, but i havent tested all backends

but suffice to say, you can do:

haxe
Toolkit.init()
Toolkit.init()
Toolkit.init()
Toolkit.init()
Toolkit.init()
Toolkit.init()
Toolkit.init()

but only the first time makes any sense / difference - subsequent calls will basically do nothing (its about loading the modules, the class map, etc)

So I should re-add it to Screen.instance? All that simple?

I'm getting this null reference error (target windows, openfl backend):

Called from hxcpp::__hxcpp_main
Called from ApplicationMain::main ApplicationMain.hx line 25
Called from ApplicationMain::create ApplicationMain.hx line 130
Called from lime.app.Application::exec lime/app/Application.hx line 150
Called from lime._internal.backend.native.NativeApplication::exec lime/_internal/backend/native/NativeApplication.hx line 146Called from lime._internal.backend.native.NativeApplication::handleMouseEvent lime/_internal/backend/native/NativeApplication.hx line 340
Called from lime.app._Event_Float_Float_Int_Void::dispatch lime/_internal/macros/EventMacro.hx line 91
hx line 178
Called from haxe.ui.backend.ComponentImpl::__onMouseEvent haxe/ui/backend/ComponentImpl.hx line 318
Called from haxe.ui.core.ComponentEvents::_onMappedEvent haxe/ui/core/ComponentEvents.hx line 114
Called from haxe.ui.core.ComponentEvents::dispatch haxe/ui/core/ComponentEvents.hx line 97
Called from haxe.ui.util.EventMap::invoke haxe/ui/util/EventMap.hx line 76
Called from haxe.ui.containers.menus._MenuBar.Events::onButtonClick haxe/ui/containers/menus/MenuBar.hx line 75
Called from haxe.ui.containers.menus._MenuBar.Events::showMenu haxe/ui/containers/menus/MenuBar.hx line 115
Critical Error: Uncatchable Throw: Null Object Reference

after changing my startup to:

haxe
Toolkit.init();
var ui = new AnimationEditorUI();
addChild(ui);

Where AnimationEditorUI is:

haxe
@:build(haxe.ui.macros.ComponentMacros.build("assets/xml/main.xml"))
class AnimationEditorUI extends VBox

And main.xml is:

xml
<vbox width="100%">
    <menubar id="menu-bar" width="100%">
        <menu text="File">
            <menuitem id="load" text="Load" />
            <menuitem id="save" text="Save" />
            <menuitem id="quit" text="Quit" />
        </menu>
    </menubar>
    ...

After some trace debugging found out that in MenuBar.hx line 115

haxe
var top = target.screenTop + (target.actualComponentHeight - Toolkit.scaleY) + componentOffset.y + menu.style.marginTop;

menu.style is null for some reason.

any chance you could zip your project? Or a minimal test case, cant repro this end

@User - yeah, screen.instance would work, or you can just add it directly to the state using your states "add"

@User - that datasource stuff in binding is fixed now (latest core), it was nothing to do with the datasource and everything to do with the component not actually being ready when the binding manager is trying to work out the value - thats sorted now